On 9/2/07, Garrett Smith <dhtmlkitchen at gmail.com> wrote:
<snip>
(moving to a new thread, as a new subject)
I'm not claiming ES is very consistent; parseInt and parseFloat are
global, not methods on Number, for example. (Now that we have "int"
and "double" classes these would be "parse" methods on those classes,
maybe -- and maybe not. After all, parseInt can return more than can
fit in an "int".)
The parseNNN methods should be moved to their respective classes.
Then, the global methods can point to these class methods, and be
deprecated.
Garrett
<snip>
On 9/3/07, Lars T Hansen <lth at acm.org> wrote:
> On 9/3/07, Garrett Smith <dhtmlkitchen at gmail.com> wrote:
> > On 9/3/07, Lars T Hansen <lth at acm.org> wrote:
> > > On 9/2/07, Garrett Smith <dhtmlkitchen at gmail.com> wrote:
<snip>
(moving to a new thread, as a new subject)
> I'm not claiming ES is very consistent; parseInt and parseFloat are
> global, not methods on Number, for example. (Now that we have "int"
> and "double" classes these would be "parse" methods on those classes,
> maybe -- and maybe not. After all, parseInt can return more than can
> fit in an "int".)
>
The parseNNN methods should be moved to their respective classes.
Then, the global methods can point to these class methods, and be
deprecated.
Garrett
<snip>
> --lars
>
On 9/3/07, Lars T Hansen <lth at acm.org> wrote:
(moving to a new thread, as a new subject)
The parseNNN methods should be moved to their respective classes. Then, the global methods can point to these class methods, and be deprecated.
Garrett
<snip>