rofl0r

> Have you thought about adding `` ? no, but feel free to add support for it. my personal plan with this project was to completely replace flex[0] in sabotage...

btw, when evaluating parser generators for own lagnuage projects the most interesting candidate i found was http://repo.hu/projects/byaccic/

> see attached just in case it can be of your interest definitely interesting, i'd happily accept a PR

hello @mingodad, what are the preconditions to experience segfault you describe in [ea6229d](https://github.com/sabotage-linux/lex/pull/2/commits/ea6229dc05cd3eb90611db3f946d1a616b9bc7d7) ? using just `lex foo.l` without -o parameter works as intended, a file called lex.yy.c is produced.

> Just don't specify an output filename so as i said above, `lex foo.l` ? works fine in my case, and sub1.c checks whether fout is NULL, else uses `lex.yy.c`...

please confirm whether #5 fixes this.

pushed 9065faa to #5 branch, i suspect that was the issue causing the generated `nc*.h` headers to contain sequences of `\r\n` instead of `\n`. please confirm whether recompiling lex with...

pushed a couple more commits to that branch. since you didnt provide a new test.c which i could vbindiff against the correct result from lex compiled on linux, i made...

that's odd. did you really check out the branch of #5 , ran make clean , and compiled everything anew ? your test.c is identical to your previous one, except...

fwiw there's a firefox plugin called cliget that hooks into the download dialog and shows a curl command line that includes the precise headers that would be sent from the...