<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Successfully Getting your Addon Reviewed</title>
	<atom:link href="http://tea.cesaroliveira.net/archives/52/feed" rel="self" type="application/rss+xml" />
	<link>http://tea.cesaroliveira.net/archives/52</link>
	<description>It&#039;s all about the cycles</description>
	<lastBuildDate>Tue, 23 Aug 2011 03:24:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: 如何治理Firefox扩展的全局命名空间污染问题 &#171; 七月佑安</title>
		<link>http://tea.cesaroliveira.net/archives/52/comment-page-1#comment-68</link>
		<dc:creator>如何治理Firefox扩展的全局命名空间污染问题 &#171; 七月佑安</dc:creator>
		<pubDate>Sun, 15 Mar 2009 11:03:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.cesaroliveira.net/?p=51#comment-68</guid>
		<description>[...] 不合理的定义全局变量，可以轻易的引发不同扩展之间的冲突，而这些完全是应该避免的（这也是AMO审阅的步骤之一），因为冲突所引发的问题是很难被发现的。就目前的开发环境来说，全局变量就是魔鬼，尤其是采用OOP开发模式的时候。 [...]</description>
		<content:encoded><![CDATA[<p>[...] 不合理的定义全局变量，可以轻易的引发不同扩展之间的冲突，而这些完全是应该避免的（这也是AMO审阅的步骤之一），因为冲突所引发的问题是很难被发现的。就目前的开发环境来说，全局变量就是魔鬼，尤其是采用OOP开发模式的时候。 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mozilla Add-ons Blog &#187; Blog Archive &#187; Firefox Extensions: Global Namespace Pollution</title>
		<link>http://tea.cesaroliveira.net/archives/52/comment-page-1#comment-67</link>
		<dc:creator>Mozilla Add-ons Blog &#187; Blog Archive &#187; Firefox Extensions: Global Namespace Pollution</dc:creator>
		<pubDate>Fri, 16 Jan 2009 16:13:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.cesaroliveira.net/?p=51#comment-67</guid>
		<description>[...] among various extensions. Something that should be always avoided (and is also part of AMO review process) since this kind of issues is very hard to find. Yes, global variables are still evil, [...]</description>
		<content:encoded><![CDATA[<p>[...] among various extensions. Something that should be always avoided (and is also part of AMO review process) since this kind of issues is very hard to find. Yes, global variables are still evil, [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

