\r
The first line of the makefiles require a definition of PCCTS_HOME.\r
\r
- These are in additiion to the AntlrMSVC50.* and DlgMSVC50.*\r
+ These are in addition to the AntlrMSVC50.* and DlgMSVC50.*\r
supplied by Jeff Vincent (JVincent@novell.com).\r
\r
#137. (Changed in MR11) Token getType(), getText(), getLine() const members\r
the variable [zz]traceOptionValueDefault is set to 0 or 1. When\r
the parser is initialized or [zz]traceReset() is called the\r
value of [zz]traceOptionValueDefault is copied to [zz]traceOptionValue.\r
- The value of [zz]traceGuessOptionValue is always initialzed to 1,\r
+ The value of [zz]traceGuessOptionValue is always initialized to 1,\r
but, as noted earlier, nothing will be reported unless\r
[zz]traceOptionValue is also positive.\r
\r
\r
The syntax of the class statement ("class parser-name {")\r
has been extended to allow for the specification of base\r
- classes. An arbirtrary number of tokens may now appear\r
+ classes. An arbitrary number of tokens may now appear\r
between the class name and the "{". They are output\r
again when the class declaration is generated. For\r
example:\r
This is especially important for predicates formed by rules\r
like the following:\r
\r
- uppperCaseVowel : <<isUpperCase(LATEXT(1))>>? vowel;\r
+ upperCaseVowel : <<isUpperCase(LATEXT(1))>>? vowel;\r
vowel: : <<isVowel(LATEXT(1))>>? LETTERS;\r
\r
These predicates are combined using AND since both must be\r
a predicate expression tree. Prior to 1.33MR10 this link was never\r
cleared and the next time the guard was used to construct a new\r
tree the link could contain a spurious reference to another element\r
- which had previosly been joined to it in the semantic predicate tree.\r
+ which had previously been joined to it in the semantic predicate tree.\r
\r
For example:\r
\r
tokens. They may not contain references to (...)+ and\r
(...)* blocks. This is now checked. This replaces the\r
fatal error message in item #78 with an appropriate\r
- (non-fatal) error messge.\r
+ (non-fatal) error message.\r
\r
In theory, context guards should be allowed to reference\r
rules. However, I have not had time to fix this.\r
correctly when the sets were of unequal sizes. Rewrote\r
set_equ to make it simpler and remove unnecessary and\r
expensive calls to set_deg(). This routine was not used\r
- in 1.33 vanila.\r
+ in 1.33 vanilla.\r
\r
#85. (Changed in 1.33MR10) Allow redefinition of MaxNumFiles\r
\r
\r
There were no changes in antlr or dlg output from the revised version.\r
\r
- The following fragment demonstates the problem by giving different\r
+ The following fragment demonstrates the problem by giving different\r
follow sets (option -pa) for var_access when built with k=1 and ck=2 on\r
1.33 vanilla and 1.33MR10:\r
\r
\r
1. start : r:rule t:Token <<$start=$r;>>\r
\r
- The $r refrence will not work when combined with\r
+ The $r reference will not work when combined with\r
the -gt option.\r
\r
2. start : t:Token <<$start=$t;>>\r
parse by "falling through". The parse can still be easily\r
resumed in other ways, but not in the most natural fashion.\r
\r
- This results in an inconsistentcy between named exception\r
+ This results in an inconsistency between named exception\r
handlers and exception handlers for alternatives. When\r
an exception handler for an alternative "falls through"\r
it goes to the nextmost outer handler - not the "normal\r
zzconsumeUntil()\r
zzconsumeUntilToken()\r
\r
-#58. (Changed in 1.33MR7) Added defintion of zzbufsize to dlgauto.h\r
+#58. (Changed in 1.33MR7) Added definition of zzbufsize to dlgauto.h\r
\r
#57. (Changed in 1.33MR7) Format of #line directive\r
\r
\r
#56. (Added in 1.33MR7) Jan Mikkelsen <janm@zeta.org.au>\r
\r
- Move PURIFY macro invocaton to after rule's init action.\r
+ Move PURIFY macro invocation to after rule's init action.\r
\r
-#55. (Fixed in 1.33MR7) Unitialized variables in ANTLRParser\r
+#55. (Fixed in 1.33MR7) Uninitialized variables in ANTLRParser\r
\r
Member variables inf_labase and inf_last were not initialized.\r
(See item #50.)\r
The reason for "Normal Action" is that the normal flow of the\r
program after a user-written exception handler is to "drop through".\r
In the case of an exception handler for a rule this results in\r
- the exection of a "return" statement. In the case of an\r
+ the execution of a "return" statement. In the case of an\r
exception handler attached to an alternative, rule, or token\r
this is the code that would have executed had there been no\r
exception.\r
\r
Repair bug introduced by 1.33MR1 for #tokdefs. The original fix\r
placed "DLGmaxToken=9999" and "DLGminToken=0" in the TokenType enum\r
- in order to fix a problem with an aggresive compiler assigning an 8\r
+ in order to fix a problem with an aggressive compiler assigning an 8\r
bit enum which might be too narrow. This caused #tokdefs to assume\r
that there were 9999 real tokens. The repair to the fix causes antlr to\r
ignore TokenTypes "DLGmaxToken" and "DLGminToken" in a #tokdefs file.\r
projects / mirror_edk2.git / blobdiff