🚀 go-pugleaf

pete@ohm.york.ac.uk (Pete French) writes:

>From article <1jeekqINN984@samson.informatik.uni-kiel.dbp.de>, by nhk@informatik.uni-kiel.dbp.de (Nils-Henner Krueger):
>> Hi,
>> 
>> I'm looking for a lex and yacc specification for OCCAM-2.
>> Does anybody know where it could be available?

>yacc for OCCAM2 is v.hard - you are probably better off writing your own
>parser. Its the indentation which makes it difficult, I havent yet seen a
>way of doing this that actually works, and if you think of one then let
>me know !

>-pete french.

>PS: If you do think of one the make sure it will handle VALOF properly - this
>    is the main problem with the indentation stuff as far as I can see.
>-- 
>-Pete French. (the -bat. )    -+ 	Are you in the militia ?
>Adaptive Systems Engineering   |
>                               +- Tuktusiuriagatigitqingnapinngitkyptinnga!

Pete,

The problem of the indentation can be solved by writing your own LEX,
the scanner part of the compiler. I have written an OCCAM-1 compiler
for the MSDOS environment. And it works.
Your remark about the VALOF function will be a small problem because
of the multiple result values, but I think it can be done with a little
trick in the parser section.

Mario Veraart
--
Mario Veraart                  TNO Physics and Electronics Laboratory
email: rioj7@fel.tno.nl        The Hague       The Netherlands
"If all else fails, show pretty pictures and animated videos, 
 and don't talk about performance",  David Bailey
-- 
Mario Veraart                  TNO Physics and Electronics Laboratory
email: rioj7@fel.tno.nl        The Hague       The Netherlands
"If all else fails, show pretty pictures and animated videos, 
 and don't talk about performance",  David Bailey