Talk:Compiler Construction/Case Study 1B

Some comments on this:
 * 1. It might be easier if you could make the source code available separately.
 * 2. Traditionally lex/flex files are *.l, yacc/bison file *.y (make has rules to deal with these file extensions automatically).
 * 3. A Makefile would be nice at some point.
 * 4. In order to be used, the code should be under a different license to GFDL. I would suggest licensing it to be used by anyone for any purpose, as its purpose is merely to be a tutorial/guide to compiler constuction.

Apart from that, it looks great.

Jonmmorgan 03:03, 8 March 2006 (UTC)

After further thought, I withdraw some of these comments. What is there is good for a tutorial. Incidental details like a Makefile are probably outside the scope of this book, though they need to be bundled with separately available source code for greater usefulness.

The licensing should not be a problem as you dual-license with Creative Commons.

211.28.122.32 13:03, 20 March 2006 (UTC)


 * And yes, that was me forgetting to sign in - very careless :).


 * Jonmmorgan 13:05, 20 March 2006 (UTC)

I really like this tutorial.

Unfortunately the "Interpreting" section has not been finished yet and i have a question how to build this interpreter. (By the way I do not know if this is the right place to ask my question.)

When interpreting, what's the best way to make a goto (goto, gotosub) jump? Will I have to parse the ast again to find the node with the matching line number and continue execution there? I could imagine that this might be difficult to code in one recursive function.

Can somebody help me? Wiegi 20:03, 25 September 2007 (UTC)