On Monday 10 September 2001 01:08 pm, Simon Cozens wrote: > 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. Oh, how many times have I heard that before? It's not a prioirty, but it's so much easier to walk the correct path from the start. Since it's all Parrot, it's even easier. -- Bryan C. Warnock [EMAIL PROTECTED]
- 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