As a parrot user, I have two feelings about this proposal 1) A very
small part of me thinks that this would improve a small consistency
nit which I've already lived with for... 4 years? 2) A much larger
part would find it another inconvenience in a long line of (each one
justifiable in its own light) inconveniences.
That said, hope for the best, but... While I'm sure it's implied, I
suggest postponing it for a .0 release (0.5.0?), but start
documenting the change and offering the new syntax as a (preferred)
option well in advance. Similar to what was done with recent items in
DEPRECATED, but with a much longer time frame.
And, assuming the goal here is consistency across the board, don't
forget about .sym. Or the Float PMC, or VTABLE methods like
"unshift_float", or methods like Parrot_floatval_time, or the
FLOATVAL macro. And collateral changes like the docs, the website and
the examples. And the book.
My 2ยข.
On Dec 19, 2005, at 8:31 PM, Joshua Isom wrote:
I was talking to Leo in the IRC room and he told me post onto the
list about proposing to change all floats to nums. Code such as
`.local float i` would instead be written as `.local num i`, but as
I gather it, current behavior would remain the same, or at least
general behavior.
