I think it's about time we decided what compiler we want to hand perl's
source to, and what language we want to implement perl in.
Currently I'm thinking C for the target compiler just because of its
ubiquity. I am *not* particularly advocating for C as a spiffy language.
Nor against, for that matter. It is, however, a language targeted at
systems work and that's pretty much what we're doing here.
As for the language we implement perl in (and thus ultimately need to
translate to the compiler-target language), I'm thinking of something like
Chip's PIL. (Or PIL itself--I've not actually seen it) Basically the
macro/tracking translator from hell that'll automagically generate header
files, provide all the permutations of vtable functions, and suchlike things.
If anyone's got any arguments in a particular direction, now would be the
time. Once we're done wrangling, we'll start in on the features we need to
write into the PIL translator, and get implementation of that started.
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
