Comments on: Ambiguous reference bug for namespaces in Flex

By: Thanks for article!

Thanks for article! — Thu, 01 Apr 2010 13:32:13 +0000

The same thing is happening when we have base class with, for example, protected setter and getter. And we inherit this class. In inherited class we override, for example, getter. Then we have the same error. To fix this we need to override getter too.

By: steve

steve — Mon, 08 Dec 2008 16:44:10 +0000

I’m coming from the .NET world and trying to learn Flex. Basic compiler bugs like this make it hard to take Flex seriously. Especially the fact that it hasn’t been fixed and is over a year old.

By: Ruben

Ruben — Sun, 02 Mar 2008 16:37:53 +0000

@tomwag: I don't entirely agree with you there. First off, it's mostly the people that call AS3 an Object Oriented language. But mainly I disagree because your problem ("this simple pattern of having a property read-only except for derived classes is not supported") has little to do with a programming-language being Object Oriented or not.

By: tomwag

tomwag — Thu, 28 Feb 2008 18:55:58 +0000

thanks for the article

it seems odd that AS3 calls itself an OOP language…but this simple pattern of having a property read-only except for derived classes is not supported…thanks Adobe!

By: Ruben

Ruben — Mon, 08 Oct 2007 19:20:41 +0000

Cool! Thanks levan

By: levan

levan — Mon, 08 Oct 2007 19:10:07 +0000

if setter namespace is known(for example public) you can do following to go around that bug.
when you refference the setter do :
myObject.public::someProperty and compiler is happy again

By: Ruben

Ruben — Sat, 25 Aug 2007 15:20:46 +0000

Ah Dano thanks so much, darn human automatism

By: Dano

Dano — Sat, 25 Aug 2007 14:25:38 +0000

Hi,

May be, you want to refer to the next code:
protected function set someProperty

Regards,
Dano