On Apr 7, 2:23 am, Joep Suijs <[email protected]> wrote:
>
> The leverage is obvious. But what is the advantage of generating
> intermediate code over C? With C
> - you can skip the learning curve
> - you can (but not have to) take advantage of the include files.
> - still have the leverage of the back ends
> - it is probably easier to debug (assuming the c-front end gives
> better error messages than the back end and the c-file is more
> readable).
>

Your arguments above sound very convincing to me. Perhaps Albert will
chime in about why the GCC approach is better.

> I am not really into language design (yet ;) but build a few parses
> (by hand) of complex configuration files, that output a list of
> 'atoms' - all elements in the encountered sequence with all irrelevant
> info (like comment, white spaces) removed and worked from there on.
> Maybe your antlr is useful to generate the first step and create such
> a list (or even a more advanced one)

Yes, Antlr can handle all of the above and more.  Antlr is roughly
equivalent to Yacc and Lex, or Bison and Flex.

Note: We would only have to run Antlr itself once, until a new JAL
language feature was added (grammar changes).

> I tried Python a few times but did not get to speed... So Perl or C
> for me please...
>

I don't mind using C, but you really should give Python another
try. :-)

> I intend to finish some of my projects before start major work on new
> one's, but this is definitely worth looking into!

Good, I'll try and work on a C version (instead of Python) of my Antlr
'snapshot' and also include a little of the output from running all of
JALLIB thru it. It is amazing how much of JALLIB is already being
parsed corrected.

We can actually do both C and Python for awhile and maybe you'll come
to like Python.

William

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/jallib?hl=en.

Reply via email to