delete onEnterFrame = null
Not only is it bad practice, it completely makes the delete meaningless.
Since onEnterFrame = null resolves to null, you're just saying delete
null. This statement is equivalent to saying only:
onEnterFrame = null;
Scott
-Original Message-
From: [EMAIL PROTECTED] on behalf of stone larsen
Sent: Thu 2/9/2006 4:55 PM
To: Flashcoders mailing list
Cc:
Subject:Re: [Flashcoders] _delete onEnterFrame vs onEnterFrame = null
delete onEnterFrame = null, is bad practice.
Scott Fanetti [EMAIL PROTECTED] wrote: delete this.onEnterFrame is definitely
the standard method. I think
null kills the function definition, but the event still gets fired and
the owner of the onEnterFrame event still gets the event notification.
delete destroys the event and removes the function pointer from the instance
Anggie Bratadinata wrote:
Hi all,
How does onEnterFrame = null differ from _delete onEnterFrame ?
Should I prefer one to the other?
___
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
-
Yahoo! Mail
Use Photomail to share photos without annoying attachments.
___
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
___
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
