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?
- Muddled Boundaries - Perl 6 vs Parrot Bryan C . Warnock
- Re: Muddled Boundaries - Perl 6 vs Parrot Simon Cozens
- Re: Muddled Boundaries - Perl 6 vs Parrot Dave Mitchell
- Re: Muddled Boundaries - Perl 6 vs Parrot Dan Sugalski
- Re: Muddled Boundaries - Perl 6 vs Parrot Dan Sugalski
- Re: Muddled Boundaries - Perl 6 vs Parrot Bryan C . Warnock
- Re: Muddled Boundaries - Perl 6 vs Parrot Nathan Torkington
- Re: Muddled Boundaries - Perl 6 vs Parrot Bryan C . Warnock
- Re: Muddled Boundaries - Perl 6 vs Parrot Simon Cozens
- Re: Muddled Boundaries - Perl 6 vs Parrot Bryan C . Warnock
- Re: Muddled Boundaries - Perl 6 vs Parrot Dan Sugalski
- Re: Muddled Boundaries - Perl 6 vs Parrot Nathan Torkington
- Re: Muddled Boundaries - Perl 6 vs Parrot Benjamin Stuhl