-
JS/CC should use the same regexp syntax as JavaScript ast this is what the user is familiar with.
In particular:
- '\xxx' support should be dropped as it is ambiguous and is not in JavaScript
- '\uXX' and '\UXXXX' should be added for full Unicode support
- '.' should have the same effect (not match end of line)
2009-07-30 00:43:04 UTC in JS/CC LALR(1) Parser Generator
-
I'm using JS/CC 0.30.
2009-07-30 00:36:17 UTC in JS/CC LALR(1) Parser Generator
-
When running jscc.exe from different directory that JS/CC's, it does not find its driver :
error: unable to open file 'driver_jscript.js_'
Workaround: run jscc.exe from its directory and use full paths to source and target files.
For an example build script that work around the bug see http://code.google.com/p/registry-files-tools/source/browse/trunk/Build.cmd.
2009-07-30 00:34:13 UTC in JS/CC LALR(1) Parser Generator
-
Currently __parse() returns an error count. There is no clean way to return %% from the top rule to the __parse() caller. The only way is to use an ugly global variable. And this makes parsing non thread safe.
Instead __parse() could return an object containing:
- src: the parsed string
- errors: the error list
- result: %% of the top grammar rule
For an attempt to implement this around...
2009-07-30 00:27:11 UTC in JS/CC LALR(1) Parser Generator
-
JS/CC should generate an object from the grammar.
- this would avoid namespace pollution
- this would make the ##PREFIX## trick useless.
As a workaround we can currently manually wrap the generated code with an object. See http://registry-files-tools.googlecode.com/svn-history/r3/trunk/msreg.par.
2009-07-30 00:20:42 UTC in JS/CC LALR(1) Parser Generator
