aboutsummaryrefslogtreecommitdiffstats
path: root/doc/gawk.info
diff options
context:
space:
mode:
Diffstat (limited to 'doc/gawk.info')
-rw-r--r--doc/gawk.info48
1 files changed, 24 insertions, 24 deletions
diff --git a/doc/gawk.info b/doc/gawk.info
index 81012210..b5d7052b 100644
--- a/doc/gawk.info
+++ b/doc/gawk.info
@@ -26967,7 +26967,7 @@ mechanisms and design remained unchanged for close to 15 years, until
`gawk' included some sample extensions, of which a few were really
useful. However, it was clear from the outset that the extension
-mechanism was bolted onto the side and was not really thought out.
+mechanism was bolted onto the side and was not really well thought out.
* Menu:
@@ -27027,9 +27027,9 @@ Some goals for the new API were:
* The API should provide _binary_ compatibility across `gawk'
releases as long as the API itself does not change.
- * The API should enable extensions written in C to have roughly the
- same "appearance" to `awk'-level code as `awk' functions do. This
- means that extensions should have:
+ * The API should enable extensions written in C or C++ to have
+ roughly the same "appearance" to `awk'-level code as `awk'
+ functions do. This means that extensions should have:
- The ability to access function parameters.
@@ -27155,9 +27155,9 @@ The API can later be expanded, in two ways:
identify the extension calling into it, should it need to know.
* Similarly, the extension passes a "name space" into `gawk' when it
- registers each extension function. This allows a future mechanism
- for grouping extension functions and possibly avoiding name
- conflicts.
+ registers each extension function. This accommodates a possible
+ future mechanism for grouping extension functions and possibly
+ avoiding name conflicts.
Of course, as of this writing, no decisions have been made with
respect to any of the above.
@@ -32513,22 +32513,22 @@ Ref: Derived Files-Footnote-31083268
Node: Future Extensions1083366
Node: Implementation Limitations1083947
Node: Extension Design1085199
-Node: Old Extension Problems1086348
-Ref: Old Extension Problems-Footnote-11087856
-Node: Extension New Mechanism Goals1087913
-Ref: Extension New Mechanism Goals-Footnote-11091272
-Node: Extension Other Design Decisions1091458
-Node: Extension Future Growth1093564
-Node: Old Extension Mechanism1094385
-Node: Basic Concepts1096125
-Node: Basic High Level1096806
-Ref: figure-general-flow1097077
-Ref: figure-process-flow1097676
-Ref: Basic High Level-Footnote-11100905
-Node: Basic Data Typing1101090
-Node: Glossary1104445
-Node: Copying1129916
-Node: GNU Free Documentation License1167473
-Node: Index1192610
+Node: Old Extension Problems1086353
+Ref: Old Extension Problems-Footnote-11087861
+Node: Extension New Mechanism Goals1087918
+Ref: Extension New Mechanism Goals-Footnote-11091284
+Node: Extension Other Design Decisions1091470
+Node: Extension Future Growth1093576
+Node: Old Extension Mechanism1094412
+Node: Basic Concepts1096152
+Node: Basic High Level1096833
+Ref: figure-general-flow1097104
+Ref: figure-process-flow1097703
+Ref: Basic High Level-Footnote-11100932
+Node: Basic Data Typing1101117
+Node: Glossary1104472
+Node: Copying1129943
+Node: GNU Free Documentation License1167500
+Node: Index1192637

End Tag Table