RE: [flexcoders] Public getter, private setter?

[Matt Chotin]

Actually on a second review I’ve been told that the engineer misunderstood the question.  The bug is in the spec, mixed visibility is intended not to be allowed (at the moment).  They’re going to discuss this further at the ECMAScript 4 Committee meeting.   Anyway, you at least know what works and doesn’t work currently J   Matt   From: flexcoders@yahoogroups.com [mailto:flexcoders@yahoogroups.com] On Behalf Of Michael Schmalle Sent: Saturday, September 09, 2006 3:58 AM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] Public getter, private setter?   Hah! So in my post a couple days ago... > This is just a guess but, I would be willing to bet this is a Player bug. I was right. hehe Peace, Mike On 9/8/06, Matt Chotin <[EMAIL PROTECTED]com> wrote: So actually we investigated further and it turns out this is a bug.  The engineer on the language team said that using mixed visibility is supposed to be allowed (I was wrong, this happens occasionally).  We have a bug filed.  Thanks for pointing it out Thunder! J   Matt   From: [EMAIL PROTECTED] ups.com [mailto:[EMAIL PROTECTED] ups.com] On Behalf Of Christian Edward Gruber Sent: Friday, September 08, 2006 6:42 AM To: [EMAIL PROTECTED]ups.com Subject: Re: [flexcoders] Public getter, private setter?   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: Matt, what has made Adobe depart from what is standard behaviour in other languages. I'm having trouble understanding any reason for this than perhaps an implementation issue (ie, we would have preferred to support independent visibility but we preferred to get it out the door without delay, since this is a relatively minor issue).   Paul ----- Original Message ----- From: Matt Chotin To: [EMAIL PROTECTED]ups.com Sent: Friday, September 08, 2006 4:48 AM Subject: RE: [flexcoders] Public getter, private setter?   It's intentional right now that a getter/setter pair must have a matching visibility modifier.  You can't change whether a variable is visible to the compiler based on whether it's being read or being written.  While we understand the use-case (and debated it internally ourselves) this is the approach we're taking right now.       -- christian gruber + process coach and architect Israfil Consulting Services Corporation email  [EMAIL PROTECTED]net + bus 905.640.1119 + mob 416.998.6023 -- What goes up, does come down. __._,_.___ -- 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 Software development tool Software development Software development services Home design software Software development company 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 __,_._,___