lex-parser
lex-parser copied to clipboard
zaach
A parser for lexical grammars used by jison.
For deep lexer rules like [ShEx's PN_CHARS_BASE](https://github.com/shexjs/shex.js/blob/b5cb30708d7c69550a07f1329aaf97cdb8eed737/packages/shex-parser/lib/ShExJison.jison#L255), the [emitted rule](https://github.com/shexjs/shex.js/blob/b5cb30708d7c69550a07f1329aaf97cdb8eed737/packages/shex-parser/lib/ShExJison.js#L934) has an enormous number of capture groups. When parsing a large input like [FHIR.shex](https://hl7.org/fhir/R4B/fhir.schema.shex.zip) gives a stack error: ``` /home/eric/checkouts/shexSpec/shex.js/packages/shex-parser/shex-parser.js:251...
Co-exists with zaach/jison#338. ## Features / Fixes / Changes - [to be edited] - fixes: + #7 + #8 + #9 / #10 / #11
It doesn't make a lick of sense to flip that switch at lexer run-time. It'd better be a compile-time setting.
Currently it is, ``` "repository": { "type": "git", "repository": "https://github.com/zaach/lex-parser.git" ``` Correct configuration,from another module, ``` "repository": { "type": "git", "url": "git://github.com/jonschlinkert/glob-base.git" ``` So second 'repository ' field should be...
We use github tarballs for debian package and without tags, we have to manually find the commits for each release and get a snapshot. But still dbeian's tools like uscan...
Would you please create a LICENSE or LICENSE.md file with your copyright information and the text of the MIT license? The MIT license specifically states that the license text must...
^ is working, but it seems to be recognized in more situations than it should. start of line is very handy when writing parsers where end-of-line is an entry delimiter...
just tried to use jison, and this got me lost for hours. $ doesn't seem to work. jison documentation points to bison, where $ is widely used. in the samples...