Hey Paul, I can't speak for Adobe, but in many other languages, accessors/mutators are simply conventions, not actual language constructs. Java, for example, has no understanding that a method is an accessor. It is merely a "bean" convention that getFoo/setFoo are getters and settors for Foo. So in many languages there is infinite freedom, but less language support. .NET, by contrast, is probably what you are comparing to with it's properties and property accessors. It might be useful to compare languages from a "desirability" standpoint, but it's often not helpful because languages are implemented differently, and each has its own implementation challenges. It's hard to say why Adobe went this way, but if accessors are more carefully managed by the language, it may be a much easier implementation to pair their access levels. regards, Christian. Paul Andrews wrote:
--
__._,_.___
christian gruber + process coach and architect Israfil Consulting Services Corporation email [EMAIL PROTECTED] + bus 905.640.1119 + mob 416.998.6023 -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
SPONSORED LINKS
Your email settings: Individual Email|Traditional
Change settings via the Web (Yahoo! ID required) Change settings via email: Switch delivery to Daily Digest | Switch to Fully Featured Visit Your Group | Yahoo! Groups Terms of Use | Unsubscribe __,_._,___ |
- Re: [flexcoders] Public getter, private setter? Christian Edward Gruber
- RE: [flexcoders] Public getter, private sette... Matt Chotin
- Re: [flexcoders] Public getter, private s... Michael Schmalle
- RE: [flexcoders] Public getter, priva... Matt Chotin
- Re: [flexcoders] Public getter, p... Michael Schmalle