 | | RE: [Flashcoders] this.onEnterFrame=undefined or delete
this.onEnterFrame | RE: [Flashcoders] this.onEnterFrame=undefined or delete
this.onEnterFrame 2004-03-14 - By EECOLOR
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.
Greetz Erik
At 15:10 14-3-2004, you wrote:
>We understand eachother now :)
>
> > So, it's actually more than just a speed issue, you could get very
> > different results if you are overriding methods.
>
>That is another aspect of this - and the effect of this could be important.
>
>That's why setting it to undefined is a bad practise, and why I don't do
>that.
>
>If anything, I set to null, like with the firstChild of an XMLNode if there
>is no child.
>
>// 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:106882
=-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --
To unsubscribe send a blank e-mail to:
Normal Mode: flashcoders-unsubscribe@(protected)
Digest Mode: flashcoders-digest-unsubscrive@(protected)
|
|
|