Welcome to the Lounge
The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
|I got a bunch of the console utilities done for my modular Parser Construction Kit
now you can do things like generate parsers and lexers, and i've almost got the bit where you can convert between different formats (so you can use Gold grammars with ANTLR or YACC, or my parser for example. or user ANTLR grammars with that same list, etc)
That's probably the coolest feature. Now people can use whatever grammars are available with whatever parsers are available.
That's still very experimental and my lexer conversion usually requires hand porting after-the-fact still.
I NEED TO SOLVE ARDEN'S THEOREM in C# to fix the above.
I'm vexed. Still, it's really amazing.
Now you can do like
@echo generating parser
ll1prep xbnf.pck | ll1gen /class XbnfParser > XbnfParser.cs
@echo generating tokenizer/lexer
ll1prep xbnf.pck | fagen /class XbnfTokenizer > XbnfTokenizer.cs
like a unix weenie
xlate xbnf.pck xbnf.gold.grm
xlate xbnf.antlr.grm xbnf.yacc.y
Now the question: the executable names are pretty general and i wanted to make them more specific to my project so you can put them in the path
the project suite is called pck so I was thinking
pll1geninstead of just ll1gen
pxlateinstead of just xlate
what do you guys think for the naming?
i want it as short as can still be reasonable. Specific enough to avoid collisions on most systems (i don't need a guarantee)
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
General News Suggestion Question Bug Answer Joke Praise Rant Admin
Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.