The update should also work on the limited developer boards such as the AmigaOne-SE and MicroA1-C Mark 2 but these will not be tested.

xenic wrote:
@Coder
I have flex in my SDK:local/c directory (not sure if it came with the SDK or I D/L it from OS4Depot) but have no idea how to use it. I know the YAM sources use flex but I never took a close look at how it's used.

Samurai_Crow wrote:
@Coder

http://piumarta.com/software/peg/ is the parser generator that Sidewinder and I were adapting for use with the Mattathias project before we sidelined it. It is written in C and should compile out of the box on OS 4 assuming you have unistd.h . It is much, MUCH easier to use than Lex and YACC and their descendents.

Deniil wrote:
@Coder

Don't we have lex/yacc? I think we do.

However I never got the point of a parser generator. Used lex/yacc in some university course once. STill don't get the point. I found writing the parser language the parser generator need and then try to understand and make use of the mess it outputs to be just as difficult as simply writing your own parser.

whose wrote:
@Coder & ChrisH

The book can be found here:

http://www.stack.nl/~marcov/compiler.pdf

Have fun!

ChrisH wrote:
@Coder
I personally recommend writing a parser manually - it's not that hard, and you get full control of it (rather than being forced to follow some complex & inflexible conventions that may not easily do what you want).

PortablE comes with the example "ToyInterpreter.e" program. Jack Crenshaw's (sp?) famous guide "Let's write a compiler" (or something like that) is a great introduction too, but he uses Pascal.

Chris wrote:
@Coder

There is also Lemon.

broadblues wrote:
@Coder

There a port of Bison about I think (or was it Yacc?). Only ever used it for ports (perl etc) though. Never used it from scratch.