meta data for this page
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
deprecated_settings [2020/10/22 17:32] – revusky | deprecated_settings [2021/01/03 00:56] – revusky | ||
---|---|---|---|
Line 18: | Line 18: | ||
* **CACHE_TOKENS**: | * **CACHE_TOKENS**: | ||
* **TRACK_TOKENS** : There is no real reason for this setting to exist any more, since, by default, Tokens are added to the AST and they have their line/column information. In fact, all Node objects have line/column information. | * **TRACK_TOKENS** : There is no real reason for this setting to exist any more, since, by default, Tokens are added to the AST and they have their line/column information. In fact, all Node objects have line/column information. | ||
- | * **COMMON_TOKEN_ACTION** : This feature is still supported but the configuration setting is no longer necessary, since JavaCC21 deduces it from the presence (or absence) of the appropriately named method in your generated lexer class. If you have a method with the signature '' | + | * **COMMON_TOKEN_ACTION** : This feature is still supported but the configuration setting is no longer necessary, since JavaCC21 deduces it from the presence (or absence) of the appropriately named method in your generated lexer class. If you have a method with the signature '' |
- | * **NODE_SCOPE_HOOK** : As with COMMON_TOKEN_OPTION, | + | * **NODE_SCOPE_HOOK** : As with the '' |
* **NODE_EXTENDS** : Since JavaCC21 has '' | * **NODE_EXTENDS** : Since JavaCC21 has '' | ||
< | < | ||
- | | + | |
</ | </ | ||
In general, code injection can be used to specify that any generated class should extend a given class or implement whatever interface(s). There is no need for a plethora of configuration settings for this. | In general, code injection can be used to specify that any generated class should extend a given class or implement whatever interface(s). There is no need for a plethora of configuration settings for this. | ||
- | The following configuration | + | The following configuration |
- | * **OUTPUT_DIRECTORY**: | ||
* **NODE_PREFIX**: | * **NODE_PREFIX**: | ||
Line 41: | Line 40: | ||
To specify the parser and lexer class names, you may use the '' | To specify the parser and lexer class names, you may use the '' | ||
- | There are a host of settings that were added //after// the FreeCC fork, which was in mid-2008. See [[ancient history]] for more information on all this. No settings added to legacy JavaCC after about 2008 are currently in JavaCC 21. Most of them are of very marginal value. Moreover, it is safe to say that nobody uses them because they are not documented anywhere that I can find! Just for example, the **GRAMMAR_ENCODING** option was added at some point after 2008 (I don't know when exactly) to specify what encoding your grammar file is in. I am certain that nobody uses this. (Or just about nobody surely.) Everybody stores their grammar files in the system default encoding which is '' | + | There are a host of settings that were added //after// the FreeCC fork, which was in mid-2008. See [[ancient history]] for more information on all this. No settings added to legacy JavaCC after about 2008 are currently |
See [[new settings in JavaCC 21]] for information on settings introduced in JavaCC21 that were not present in legacy JavaCC. | See [[new settings in JavaCC 21]] for information on settings introduced in JavaCC21 that were not present in legacy JavaCC. | ||