At 03:55 PM 9/10/2001 +0100, Dave Mitchell wrote:
>Bryan C. Warnock" <[EMAIL PROTECTED]> wrote:
> > Erk, we seem to be muddling around in that great grey area between what is
> > Parrot and what is Perl.
>
>Yes, which leads me on to think...
>
>(With my "maintainer of the Coding PDD" hat on)
>
>Presumably we have to decide what bits of code have a Parrot_ prefix,
>and what bits are Perl_. And do we split off everything into two completely
>independent src trees, perhaps which compile to libparrot.a and libperl.a?
>Or this articifcal separation too hard to achieve in practice?
We aren't going to split things out that hard. Generally speaking, the
language-specific pieces will be:
1) Parser rules
2) Possibly compiler rules (maybe)
3) Variable vtable things
So pretty much everything should have a Parrot_ prefix on it, with the
(possible) exception of the perl variable vtable code. (Though I think
those should probably be Parrot_ as well. We can change them to Perl_ at
some point if it becomes appropriate)
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
