develooper Front page | perl.bootstrap | Postings from July 2000

implementation strategy (was Re: Working Group Proposal)

Joshua N Pritikin
July 20, 2000 09:36
implementation strategy (was Re: Working Group Proposal)
Message ID:
On Thu, Jul 20, 2000 at 09:14:01AM -0700, wrote:
> This is how I would do it:
> Build a meta-language system using Perl5 that allows
> you to define a new language. The output of the system
> would be C++ code that implements the new langauge.

It doesn't have to be so formalized.  The "meta-language" could be a mix
of perl5 and configuration files, or a group of domain specific

> This means you write the language in a meta-language
> specifically tailored to building new languages (defined
> by us), and you never touch C++ code directly.

"never touch C++ code directly" -- YES!

> This
> also allows us to change the C++ code generated as
> need to account for oddities with different platforms
> and compilers.


> The reasons for going with C++:
> - Portable across many platforms
> - Standard Template Library
> - Large community of programmers
> - Feature rich

I'm not sure whether these advantages hold when using C++ strictly as a
target for a code generator.  In any case, I don't feel strongly.  It
should be (relatively) easy to retarget the backend.

May the best description of competition prevail.
      (via, but not speaking for Deutsche Bank) Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About