Use the longer form and encourage people to use editors with auto complete... that gives you literary code while perserving quick typing. Also, that aside, in STL there's often some types that are awkwardly long to use in statements (ie, stuff like vector<fooBar>::const_iterator in a loop initializer). A typical solution is to use a typdef that defines something like CI or VfBCI. At least that way, the abbreviation is documented in the code, and someone reading it doesn't have to go to an external source to learn what the abbreviation means.
- Anachronistic Acronyms in Parrot? Paul Prescod
- 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
