Ok,
A lot of this stuff sometimes I "don't" get right off that bat. I'm
getting back into js, which is a good thing. :) So this issues, I just
don't quite understand at the moment but I don't need to either. ;-)
I will leave it up to you to say, Mike "this is missing, fix it" type
stuff, then everything works really quickly. :)
Mike
Quoting Frank Wienberg <fr...@jangaroo.net>:
BTW, my question about native was wrong, you had already answered why you
use native, I MEANT to ask why you took the !native calls out
Ha, funny that was the only thing I *didn't* answer :-)
But my explanation of why use "native!" anyway hints at why I took it out
for some classes, so there is an additional rule:
If the global JavaScript object is top-level (not a property of a
"package"/namespace object) *and* it is not aliased *and* not "polyfilled",
I though defining a local variable with the same name wouldn't make sense.
This holds true for example for "String" and "parseInt".
-Frank-
--
Michael Schmalle - Teoti Graphix, LLC
http://www.teotigraphix.com
http://blog.teotigraphix.com
