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

RE: Working Group Proposal

Thread Previous | Thread Next
From:
lem
Date:
July 20, 2000 06:54
Subject:
RE: Working Group Proposal
Message ID:
139101bff251$9f43d9c0$1101800a@datacenter.cha.cantv.net

Please forgive me as I'm getting late to this thread...

Writing perl in perl has a number of interesting side effects, one of which is indeed a perl-to-whatever
translator (C, C++, etc). In any case, the translator would essentially be a C/C++ program itself.

Also note that if going ahead with the writing of perl in perl, the choice for the underlying language is probably irrelevant, with the exception of the "perl embedding".

Said translator or code generator could be written in perl5. This would give us at least, a reference to a piece of perl5 code that would always be "upwards" compatible with perl6 :)

-lem


-----Original Message-----
From:	"Piers Cawley" <pdcawley@bofh.org.uk>
Sent:	Thursday, July 20, 2000 9:21 AM
To:	"Joshua N Pritikin" <joshua.pritikin@db.com>
Cc:	"kstar@chapin.edu" <kstar@chapin.edu>, "bootstrap@perl.org" <bootstrap@perl.org>
Subject:	Re: Working Group Proposal

Joshua N Pritikin <joshua.pritikin@db.com> writes:

> 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.

I was thinking the plan was to be able to write perl in perl. I kind
of assumed that this would mean that there would be a rather more
fully blown perl compiler that produced 'real' machine language
(either via C or directly).

Which seems a tad ambitious, but it would be very nice.

-- 
Piers

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About