 | | | this.onEnterFrame=undefined or delete this.onEnterFrame | this.onEnterFrame=undefined or delete this.onEnterFrame 2004-03-14 - By Morten Barklund
Back
> Like something said before. Setting to undefined is not a bad practice,
> this depends on the case u are using it in. In some cases setting
> values to
> undefined can improve speed. There can also be situations where u want a
> value to be undefined and not resolve via the prototype chain.
I'd anytime recommend setting to null only - never set to undefined. You can
have the same speed improvements, but it works another way.
If I check a variable or property, and it is undefined, I'd expect it to be
non-existent - not set to undefined and thus maybe hiding prototyped
properties.
That was my point ;)
// Morten Barklund
// DKMMUG Manager
=-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --
Supported by Fig Leaf Software
=-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --
Be sure to check the archives and the wiki:
http://chattyfig.figleaf.com/
=-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --
http://chattyfig.figleaf.com/cgi-bin/ezmlm-cgi?1:mss:106884
=-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --
To unsubscribe send a blank e-mail to:
Normal Mode: flashcoders-unsubscribe@(protected)
Digest Mode: flashcoders-digest-unsubscrive@(protected)
|
|
|