: That is on purpose, for now. The idea was to introduce a new functionnality
: without changing the way things worked before. But yes, it would be possible
: to make it so that, if wanted, the English operators could be "disabled".
Hmmm... i think i see what you mean, eliminating the english operators
from the grammer would currently require that an English bundle be used
... and you wanted the Locale/bundle specifications to be entirely
optional right?
as i said, i'm not very familiar with JavaCC. ... but couldn't the action
for AND, NOT, and OR gain a similar code block like the one you added for
TERM -- but would do the opposite based on useLocalizedOperators ? ... i'm
guessing it owuld be something like...
<AND: ("AND" | "&&") >
{
if (useLocalizedOperators){
matchedToken.kind = TERM;
}
...that way if localized operators are turnd on, AND will be treated like
a regular term, but if they aren't the grammer is still the same as it
allways was. Right?
: Give me a few days, I'll take the time to submit a new version of the patch
: with the suggested enhancements.
That would be really great. One of these days i need to dust of my
Flex/Yak/Bison books and remind myself how parsers and grammers work so i
can help out more on stuff like this.
-Hoss
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
