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: | "=?iso-8859-1?q?C=E9dric_LEMAIRE?=" <codeworker@free.fr> |
Newsgroups: | comp.compilers |
Date: | 8 Jun 2005 16:00:25 -0400 |
Organization: | http://groups.google.com |
References: | 05-06-00405-06-018 05-06-031 05-06-036 |
Keywords: | translator, tools |
Posted-Date: | 08 Jun 2005 16:00:25 EDT |
>Recently I've become aware of a new tool by Cedric LEMAIRE
> that also appears to cover the gap.
Yes, I think the source-to-source translation provided by CodeWorker, a
parsing tool and a source code generator (distributed under LGPL and
available at "http://www.codeworker.org"), will cover your need.
You write a translation script, which melt both extended BNF rules (to
parse your semi-C++ file) and template-based scripts to translate your
script to C++ on-the-fly. The embedded C++ will just be copied via the
'#implicitCopy' mechanism used in CodeWorker to transform source code.
P.S.: There is a little spelling mistake on my family name: Lemaire,
not Lamaire!
Return to the
comp.compilers page.
Search the
comp.compilers archives again.