Dan Sugalski writes: > Not at the Parrot level they aren't. They might be faked out to be so at > the Perl/Python/Ruby level, though. Would it not make more sense for Parrot types to be first-class objects for the language being implemented? It seems this would make things easier both for the upper-level runtimes and for multiple-language applications. -Fred -- Fred L. Drake, Jr. <fdrake at acm.org> PythonLabs at Zope Corporation
- Re: Anachronistic Acronyms in Parrot? Simon Cozens
- Re: Anachronistic Acronyms in Parrot? Dan Sugalski
- Re: Anachronistic Acronyms in Parrot? Samuele Pedroni
- Re: Anachronistic Acronyms in Parrot? Mathieu Bouchard
- Re: Anachronistic Acronyms in Parrot? Kurt D. Starsinic
- Re: Anachronistic Acronyms in Parrot? Dan Sugalski
- Re: Anachronistic Acronyms in Parrot? Paul Prescod
- Re: Anachronistic Acronyms in Parrot? Dan Sugalski
- Re: Anachronistic Acronyms in Parrot? Paul Prescod
- Re: Anachronistic Acronyms in Parrot? Dan Sugalski
- Re: Anachronistic Acronyms in Parrot? Fred L. Drake, Jr.
- Re: Anachronistic Acronyms in Parrot? Dan Sugalski
- RE: Anachronistic Acronyms in Parrot? Hong Zhang
- Re: Anachronistic Acronyms in Parrot? Paul Prescod
- RE: Anachronistic Acronyms in Parrot? Samuele Pedroni
- RE: Anachronistic Acronyms in Parrot? Dan Sugalski
- Re: Anachronistic Acronyms in Parrot? Dan Sugalski
- RE: Anachronistic Acronyms in Parrot? Samuele Pedroni
- RE: Anachronistic Acronyms in Parrot? Hong Zhang
- RE: Anachronistic Acronyms in Parrot? Dan Sugalski
- Re: Anachronistic Acronyms in Parrot? Paul Prescod
