Front page | perl.bootstrap |
Postings from July 2000
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. 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. 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 At 11:53 AM 7/20/2000 -0400, Joshua N Pritikin wrote: >On Thu, Jul 20, 2000 at 11:29:34AM -0400, jdporter@min.net wrote: > > Joshua N Pritikin wrote: > > > On a more serious note, will perl6 be written in C or C++? If C, then I > > > suggest that we avoid actually writing any C by hand, and instead write > > > a perl5 code generator for each major component. > > > > My humble suggestion: Objective C. > >As a target for the code generator? Sure, whatever. Maybe a picture >will help: > > Perl5 => Intermediate Representation (C or C++ or Obj-C) => Perl6 > >The part I want to emphasize is that Perl6 should not be written in a >low-level language. Chip's Topaz idea was to use C++ instead of C. >Maybe C++ is still too low-level. I propose that perl6 be written >exclusively in perl5. > >-- >May the best description of competition prevail. > (via, but not speaking for Deutsche Bank)