Paul Prescod <[EMAIL PROTECTED]>
> If one presumes that Parrot is going to be so much nicer than the
> current Perl internals that many more people will be interested in it,
> then maybe it makes sense to make names as readable as possible, even if
> they are not what Perl historically used.
>
> 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. :^)
Donal.
--
Donal K. Fellows, Department of Computer Science, University of Manchester, UK.
(work) [EMAIL PROTECTED] Tel: +44-161-275-6137 (preferred email addr.)
(home) [EMAIL PROTECTED] Tel: +44-1274-401017 Mobile: +44-7957-298955
http://www.cs.man.ac.uk/~fellowsd/ (Don't quote my .sig; I've seen it before!)
