<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.12-alpha" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: E4X: Not as awful as I thought</title>
	<link>http://www.lshift.net/blog/2008/05/07/e4x-not-as-awful-as-i-thought</link>
	<description>What happens at LShift</description>
	<pubDate>Sat, 11 Oct 2008 23:20:11 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.12-alpha</generator>

	<item>
		<title>by: tonyg</title>
		<link>http://www.lshift.net/blog/2008/05/07/e4x-not-as-awful-as-i-thought#comment-94765</link>
		<pubDate>Wed, 07 May 2008 13:29:44 +0000</pubDate>
		<guid>http://www.lshift.net/blog/2008/05/07/e4x-not-as-awful-as-i-thought#comment-94765</guid>
					<description>&lt;p&gt;Agreed, Tom. Having standardised DOM/E4X integration would be excellent.&lt;/p&gt;

&lt;p&gt;WRT monkey-patching - according to &lt;a href="http://en.wikipedia.org/wiki/Monkey_patch" rel="nofollow"&gt;wikipedia on the subject&lt;/a&gt;, the term actually did start off as guerilla-patch!&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Agreed, Tom. Having standardised DOM/E4X integration would be excellent.</p>
<p>WRT monkey-patching - according to <a href="http://en.wikipedia.org/wiki/Monkey_patch" rel="nofollow">wikipedia on the subject</a>, the term actually did start off as guerilla-patch!</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Tom Berger</title>
		<link>http://www.lshift.net/blog/2008/05/07/e4x-not-as-awful-as-i-thought#comment-94758</link>
		<pubDate>Wed, 07 May 2008 12:37:30 +0000</pubDate>
		<guid>http://www.lshift.net/blog/2008/05/07/e4x-not-as-awful-as-i-thought#comment-94758</guid>
					<description>&lt;p&gt;I like the term "guerilla-patching". We usually call it "monkey-patching". Maybe a good compromise between the two would be to call it "gorilla-patching"!&lt;/p&gt;

&lt;p&gt;It would not only be nice to get E4X integrated with the rest of the language, but also with the host. The fact that an E4X tag object is different from a browser's equivalent document object (when hosted in a browser) is ridiculous, and renders it quite useless for &lt;em&gt;the&lt;/em&gt; killer app for this feature.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I like the term &#8220;guerilla-patching&#8221;. We usually call it &#8220;monkey-patching&#8221;. Maybe a good compromise between the two would be to call it &#8220;gorilla-patching&#8221;!</p>
<p>It would not only be nice to get E4X integrated with the rest of the language, but also with the host. The fact that an E4X tag object is different from a browser&#8217;s equivalent document object (when hosted in a browser) is ridiculous, and renders it quite useless for <em>the</em> killer app for this feature.</p>
]]></content:encoded>
				</item>
</channel>
</rss>
