One place that is somewhat painful for me is when dealing with
interfaces and vars vs. getters/setters. Most of the time my
interfaces use methods only, but there are occasions where it makes
sense to toss a property in there. Since you can't have var in an
interface, I find myself writing
Yes, we're doing it -- in fact, Scott Evans, the developer who is implementing
this feature,
named his whole blog after it! http://gettingandsetting.com/
- Mike Morearty, Flex Builder team
--- In flexcoders@yahoogroups.com, Gregor Kiddie [EMAIL PROTECTED] wrote:
I believe this is already
Please remember that if all you need is default behavior as the script
you provided does, that is implicitly provided by creating your var
public in AS3.
Yes, it feels funny having a public member variable coming from Java
since it is bad to expose your objects state. But, if you need to
You're getting into religious war territory there my friend! One that's
been doing the blogs recently too...
The OP wanted a way of generating getters / setters automatically...
If we are running a master class here... I would suggest that you only
ever generate getters for your model, and
Obviously I would not suggest breaking encapsulation. I guess I would
suggest not 'generating' accessors/mutators rather give it thought and
add them as you should. Also I was trying, although I admit poorly,
to make sure a Java developer coming into Flex/AS3 does not miss some
of the powerful
5 matches
Mail list logo
