On Mon, Sep 10, 2001 at 10:58:33AM -0600, Nathan Torkington wrote: > let's assume that Parrot will only officially be part of the Perl project, > and focus on writing more Parrot code instead of arguing about > namespaces. What He Said. And in addition - why are we worrying about namespace collision RIGHT NOW? Sure, when Parrot can be embedded, then we should ensure that our names aren't going to clash. But who in their right minds is going to embed Parrot in anything in its current state? (Leon, I said "in their right minds") It's not a priority, compared to getting working code out there. We can sort it out later. Simon
- 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
- Re: Muddled Boundaries - Perl 6 vs Parrot Simon Cozens
- Re: Muddled Boundaries - Perl 6 vs Parrot Benjamin Stuhl
- 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 Simon Cozens