Is there an easier-to-use alternative to bison/flex/yacc/etc for writing parsers?
It's not that I don't understand computer grammar theory. It's that the documentation and syntax for these programs suck ass. Richard Stallman fails at documenting his faggotry, not sorting things neatly and omitting needed details. And examples that work in the info files result in error messages when used with these programs.
Name:
Anonymous2007-01-27 18:43
I thought Flex and Bison were a piece of cake. I ignored the documentation, and made use of a few good examples to start experimenting.
I'm with >>2. Once I started using Flex and Bison, I wanted to make sweet love to them because it was so much easier/more powerful than ad-hoc. I kept all my code from college, if you want I have a semi-recent example that might work for you. Want?
it seems to me you're almost always better off writing your own lexer and feeding yacc that way. theres an orly book on yacc that is pretty decent, and mks makes a yacc too.
Bringing /prog/ back to its people
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy