Re: Anachronistic Acronyms in Parrot?

[Nathan Torkington]

I slept in on the wrong day :-) I think we should retrofit longer
names.  I have two reasons why:

(1) We said we were going to write it cleanly first and then optimize
    later.  I think this should apply just as much to symbol names as
    to algorithms.

(2) We want to encourage casual hackers.  It's easy to reject or
    modify a bad patch.  As we've learned with perl5, it can be very
    hard to get patches at all.  Also, casual hackers aren't just
    adding features, often they're fixing bugs--Mozilla has
    successfully used QA to get new hackers into the fold, training
    them on bug fixes and working them up to being fully-fledged core
    hackes.

And after writing that response, I see Simon has capitulated  :-)

If those of you from other languages could point us to URLs explaining
your source naming conventions, I'm sure it'll make Simon's life much
easier.  Thanks,

Nat