<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Ambiguous reference bug for namespaces in Flex</title>
	<atom:link href="http://www.rubenswieringa.com/blog/ambiguous-reference-bug-for-namespaces-in-flex/feed" rel="self" type="application/rss+xml" />
	<link>http://www.rubenswieringa.com/blog/ambiguous-reference-bug-for-namespaces-in-flex</link>
	<description>Ruben writes flashy writings</description>
	<pubDate>Fri, 21 Nov 2008 04:51:28 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Ruben</title>
		<link>http://www.rubenswieringa.com/blog/ambiguous-reference-bug-for-namespaces-in-flex#comment-20396</link>
		<dc:creator>Ruben</dc:creator>
		<pubDate>Sun, 02 Mar 2008 16:37:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.rubenswieringa.com/blog/ambiguous-reference-bug-for-namespaces-in-flex#comment-20396</guid>
		<description>&lt;strong&gt;@tomwag:&lt;/strong&gt; I don't entirely agree with you there. First off, it's mostly the people that call &lt;abbr&gt;AS3&lt;/abbr&gt; an Object Oriented language.

But mainly I disagree because your problem (&lt;em&gt;"this simple pattern of having a property read-only except for derived classes is not supported"&lt;/em&gt;) has little to do with a programming-language being Object Oriented or not.</description>
		<content:encoded><![CDATA[<p><strong>@tomwag:</strong> I don&#8217;t entirely agree with you there. First off, it&#8217;s mostly the people that call <abbr>AS3</abbr> an Object Oriented language.</p>
<p>But mainly I disagree because your problem (<em>&#8220;this simple pattern of having a property read-only except for derived classes is not supported&#8221;</em>) has little to do with a programming-language being Object Oriented or not.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tomwag</title>
		<link>http://www.rubenswieringa.com/blog/ambiguous-reference-bug-for-namespaces-in-flex#comment-20010</link>
		<dc:creator>tomwag</dc:creator>
		<pubDate>Thu, 28 Feb 2008 18:55:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.rubenswieringa.com/blog/ambiguous-reference-bug-for-namespaces-in-flex#comment-20010</guid>
		<description>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!</description>
		<content:encoded><![CDATA[<p>thanks for the article</p>
<p>it seems odd that AS3 calls itself an OOP language&#8230;but this simple pattern of having a property read-only except for derived classes is not supported&#8230;thanks Adobe!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ruben</title>
		<link>http://www.rubenswieringa.com/blog/ambiguous-reference-bug-for-namespaces-in-flex#comment-6754</link>
		<dc:creator>Ruben</dc:creator>
		<pubDate>Mon, 08 Oct 2007 19:20:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.rubenswieringa.com/blog/ambiguous-reference-bug-for-namespaces-in-flex#comment-6754</guid>
		<description>Cool! Thanks levan :)</description>
		<content:encoded><![CDATA[<p>Cool! Thanks levan <img src='http://www.rubenswieringa.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: levan</title>
		<link>http://www.rubenswieringa.com/blog/ambiguous-reference-bug-for-namespaces-in-flex#comment-6753</link>
		<dc:creator>levan</dc:creator>
		<pubDate>Mon, 08 Oct 2007 19:10:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.rubenswieringa.com/blog/ambiguous-reference-bug-for-namespaces-in-flex#comment-6753</guid>
		<description>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 :)</description>
		<content:encoded><![CDATA[<p>if setter namespace is known(for example public) you can do following to go around that bug.<br />
 when you refference the setter do  :<br />
myObject.public::someProperty and compiler is happy again <img src='http://www.rubenswieringa.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ruben</title>
		<link>http://www.rubenswieringa.com/blog/ambiguous-reference-bug-for-namespaces-in-flex#comment-2541</link>
		<dc:creator>Ruben</dc:creator>
		<pubDate>Sat, 25 Aug 2007 15:20:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.rubenswieringa.com/blog/ambiguous-reference-bug-for-namespaces-in-flex#comment-2541</guid>
		<description>Ah Dano thanks so much, darn human automatism ;)</description>
		<content:encoded><![CDATA[<p>Ah Dano thanks so much, darn human automatism <img src='http://www.rubenswieringa.com/blog/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dano</title>
		<link>http://www.rubenswieringa.com/blog/ambiguous-reference-bug-for-namespaces-in-flex#comment-2539</link>
		<dc:creator>Dano</dc:creator>
		<pubDate>Sat, 25 Aug 2007 14:25:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.rubenswieringa.com/blog/ambiguous-reference-bug-for-namespaces-in-flex#comment-2539</guid>
		<description>Hi,

May be, you want to refer to the next code:
&lt;em&gt;protected function set someProperty&lt;/em&gt;

Regards,
Dano</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>May be, you want to refer to the next code:<br />
<em>protected function set someProperty</em></p>
<p>Regards,<br />
Dano</p>
]]></content:encoded>
	</item>
</channel>
</rss>
