Related articles |
---|
simple code translator - suggestions? makc.the.great@gmail.com (makc.the.great) (2005-06-02) |
Re: simple code translator - suggestions? haberg@math.su.se (2005-06-02) |
Re: simple code translator - suggestions? haberg@math.su.se (2005-06-04) |
Re: simple code translator - suggestions? cfc@shell01.TheWorld.com (Chris F Clark) (2005-06-06) |
Re: simple code translator - suggestions? haberg@math.su.se (2005-06-08) |
Re: simple code translator - suggestions? bettini@dsi.unifi.it (Lorenzo Bettini) (2005-06-08) |
Re: simple code translator - suggestions? codeworker@free.fr (=?iso-8859-1?q?C=E9dric_LEMAIRE?=) (2005-06-08) |
Re: simple code translator - suggestions? idbaxter@semdesigns.com (Ira Baxter) (2005-06-23) |
From: | haberg@math.su.se (Hans Aberg) |
Newsgroups: | comp.compilers |
Date: | 4 Jun 2005 23:40:11 -0400 |
Organization: | Mathematics |
References: | 05-06-004 05-06-018 |
Keywords: | translator |
Posted-Date: | 04 Jun 2005 23:40:11 EDT |
>> But this can be automated by calling a suitable program in the
>> parser actions, able to sort it out. Perhaps output can be
>> generated by a macro program like say M4, but it may be better to
>> use Guile, in the output actions.
> [I was also going to suggest M4. It's ugly, but often no more ugly
> than the alternatives. -John]
This is an interesting observation, because Bison is about to switch
from using M4 to probably Guile, when writing out the skeleton files:
It became simply too difficult to do it via M4. There is supposed to
be an experimental Bison-Guile version somewhere.
Perhaps there is a gap here -- a program made especially good for
"pretty-printing" or "expressing" via parser actions.
--
Hans Aberg
Return to the
comp.compilers page.
Search the
comp.compilers archives again.