On Thu, Sep 20, 2001 at 10:53:11AM +0100, Chris boris Ross wrote:
> documenting) which in turn means more people can pick up the source code and
> understand and contribute, which is kinda the crux of OpenSource isn't it?
Do you really want to encourage people to pick up something as complex as
Parrot and start contributing without looking at the gestalt of how it works?
We get enough uninformed patches as it is. :)
--
If a 6600 used paper tape instead of core memory, it would use up tape
at about 30 miles/second.
-- Grishman, Assembly Language Programming
- Re: Anachronistic Acronyms in Parrot? Jason Watkins
- RE: Anachronistic Acronyms in Parrot? Brent Dax
- Re: Anachronistic Acronyms in Parrot? Dan Sugalski
- Re: Anachronistic Acronyms in Parrot? Sterling Hughes
- Re: Anachronistic Acronyms in Parrot? Simon Cozens
- Re: Anachronistic Acronyms in Parrot? Paul Prescod
- Re: Anachronistic Acronyms in Parrot? Donal K. Fellows
- Re: Anachronistic Acronyms in Parrot? Stephane Payrard
- Re: Anachronistic Acronyms in Parrot? David Cantrell
- Re: Anachronistic Acronyms in Parrot? boris
- Re: Anachronistic Acronyms in Parrot? Simon Cozens
- Re: Anachronistic Acronyms in Parrot? Guido van Rossum
- Re: Anachronistic Acronyms in Parrot? Guido van Rossum
- Re: Anachronistic Acronyms in Parrot? Simon Cozens
- Re: Anachronistic Acronyms in Parrot? Guido van Rossum
- Re: Anachronistic Acronyms in Parrot? Simon Cozens
- Re: Anachronistic Acronyms in Parrot? Guido van Rossum
- Re: Anachronistic Acronyms in Parrot? Donal K. Fellows
- Re: Anachronistic Acronyms in Parrot? Simon Cozens
- Re: Anachronistic Acronyms in Parrot? Guido van Rossum
- Re: Anachronistic Acronyms in Parrot? boris
