Re: Anachronistic Acronyms in Parrot?

[Guido van Rossum]

> > I propose, for example, "intval" for IV and "floatval" for NV.
> 
> As a Tcl'er, I reckon that even "intval" and "floatval" are not
> *sufficiently* verbose.  Were this following the principles set out in
> http://tcl.sourceforge.net/engManual.pdf (which have worked very well
> in Tcl development over a long period) I'd be reckoning on calling
> them something more like "intValue" and "floatValue" (they are members
> of a structure/union, aren't they?)  That style of naming might take
> longer to type, but it takes much less time to read and understand,
> especially for someone who is not a deep expert in that code.  :^)

Hear, hear.  Amen.

We use long names for most things except local variables in the Python
source code, and it definitely makes the code more accessible to
part-time developers.

--Guido van Rossum (home page: http://www.python.org/~guido/)