Re: Tutorial question (Jack Crenshaw)

On 19 Dec 2002, Fis}{ wrote:
[SNIP]
>
> I would like to know if there is any interest in further tutorials
> based on the ones that Jack Crenshaw wrote. Maybe this is old history
> and technique has evolved, I don't know.


I also translated Jack Crenshaw's tutorials to JavaScript with x86 code
generation. I was able to translate through tutorial 3 before I had to
take care of midterms. I'm using an extended version of the C-based
JavaScript Intrepreter that is included in the Mozilla Project (the
SpiderMonkey JavaScript Engine <http://www.mozilla.org/js/spidermonkey/>).
I added some necessary "C-style" file IO methods to the interpreter and a
couple other utility methods that I found useful. Currently, I have my
version of the JS Interpreter building on MacOSX, Linux, and an older
version of SpiderMonkey building on DOS though I am sure one version or
the other will build on Win32 with either CygWin or MinGW. Everything I
added has an ANSI/POSIX C implementation.


Getting back to the point...I stopped my translations because I wished to
implement Jack's use of Pascal's set comparison in a JS module.
Personally, I always missed Pascal's set comparison when I began learning
other languages like C, C++, Java. Being able to write


if( c in [ '', TAB ] ) {...}


always seemed pretty cool to me. Far cleaner and easier to read than a
long switch-case statement. Really, I would like to see an updated
version of Jack Crenshaw's tutorials and I might be interested spending
some time on this. Personally, I would like to see them written in either
C with heavy use of modern data structures (lists and trees derived from
struct's) or Java. A JavaScript implementation wouldn't be so bad either,
IMO. I think some consolidation of concepts and techniques would also be
in order. If you need some help, I'd be willing to read over your work
and offer my opinions and suggestions. Contact me off ng.


Louis


slshmeat@sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org

Return to the comp.compilers page.
Search the comp.compilers archives again.