That's exactly why I prefer using them.
Implicit getter/settters allow you do define a property (variable) of a class
and do something when the property changes.
So you get to keep the clear distinction between a "property" and a "method" of
a class (from a user perspective).
regards,
Muzak
----- Original Message -----
From: "Matthias Dittgen" <[EMAIL PROTECTED]>
To: "Flashcoders mailing list" <flashcoders@chattyfig.figleaf.com>
Sent: Wednesday, February 14, 2007 8:54 AM
Subject: Re: [Flashcoders] Coding Standards: Use of Get/Set
> You always compare "implicit getter/settter" with "explicit getter/setter".
> Just a thought of mine is to compare "implicit getter/setter" with
> public variables.
>
> When you use someClass, that was written by someone else, you do not
> know if the following code uses "implicit getter/setter" or is just a
> public variable:
> someClassInstance._fancy = 10
>
> If it is an "implicit getter/setter", it can do for example some kind
> of event handling, like like calling onFancy() or broadcast("onFancy")
> everytime you set the _fancy property.
>
> So "implicit getter/setter" are hiding such things effectivly from the
> user of you classes.
>
> Matthias
>
_______________________________________________
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
