<?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 for kennethjorgensen.com</title>
	<atom:link href="http://kennethjorgensen.com/blog/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://kennethjorgensen.com/blog</link>
	<description></description>
	<lastBuildDate>Mon, 12 Mar 2012 23:20:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4</generator>
	<item>
		<title>Comment on On PHP 5.4 and Traits by kenn</title>
		<link>http://kennethjorgensen.com/blog/2012/03/06/on-php-5-4-and-traits/comment-page-1/#comment-341</link>
		<dc:creator>kenn</dc:creator>
		<pubDate>Mon, 12 Mar 2012 23:20:00 +0000</pubDate>
		<guid isPermaLink="false">http://kennethjorgensen.com/blog/?p=150#comment-341</guid>
		<description>Duely noted and corrected. Thanks for the heads up. That&#039;s what happens when you copy-paste without don&#039;t pay attention.

Yes that&#039;s exactly what I meant regarding renaming the internal variable. Since it&#039;s not private to the trait itself, but rather becomes private to the class, it causes a collision. Additionally it inserts extra aliased methods rather than straight renaming. In my research I did stumble upon &lt;a href=&quot;https://wiki.php.net/rfc/horizontalreuse&quot; rel=&quot;nofollow&quot;&gt;some talk about grafts&lt;/a&gt;, which looks more like what I was expecting. I&#039;ve used traits a little bit in my own code now to get a proper feel for it, and it does make writing various getters and setters a lot easier.</description>
		<content:encoded><![CDATA[<p>Duely noted and corrected. Thanks for the heads up. That&#8217;s what happens when you copy-paste without don&#8217;t pay attention.</p>
<p>Yes that&#8217;s exactly what I meant regarding renaming the internal variable. Since it&#8217;s not private to the trait itself, but rather becomes private to the class, it causes a collision. Additionally it inserts extra aliased methods rather than straight renaming. In my research I did stumble upon <a href="https://wiki.php.net/rfc/horizontalreuse" rel="nofollow">some talk about grafts</a>, which looks more like what I was expecting. I&#8217;ve used traits a little bit in my own code now to get a proper feel for it, and it does make writing various getters and setters a lot easier.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on On PHP 5.4 and Traits by KB Jørgensen</title>
		<link>http://kennethjorgensen.com/blog/2012/03/06/on-php-5-4-and-traits/comment-page-1/#comment-340</link>
		<dc:creator>KB Jørgensen</dc:creator>
		<pubDate>Mon, 12 Mar 2012 22:47:24 +0000</pubDate>
		<guid isPermaLink="false">http://kennethjorgensen.com/blog/?p=150#comment-340</guid>
		<description>It is a good addition and certainly has its uses. You didn&#039;t give any code examples and I didn&#039;t bother to check for myself, but I assume you meant that it&#039;s not possible to just rename the private variable $address to something like $shippingAddress and $billingAddress just like it&#039;s possible with the getter and setter functions. If that&#039;s the case, I&#039;m sure it&#039;ll be changed in later versions, since I don&#039;t see any reason why that should happen by design.

Btw, you repeated the post twice. You might wanna edit it and make it just say things once. :)</description>
		<content:encoded><![CDATA[<p>It is a good addition and certainly has its uses. You didn&#8217;t give any code examples and I didn&#8217;t bother to check for myself, but I assume you meant that it&#8217;s not possible to just rename the private variable $address to something like $shippingAddress and $billingAddress just like it&#8217;s possible with the getter and setter functions. If that&#8217;s the case, I&#8217;m sure it&#8217;ll be changed in later versions, since I don&#8217;t see any reason why that should happen by design.</p>
<p>Btw, you repeated the post twice. You might wanna edit it and make it just say things once. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on BitCoin: A Quick Introduction by TumuTanzi</title>
		<link>http://kennethjorgensen.com/blog/2011/06/12/bitcoin-a-quick-introduction/comment-page-1/#comment-100</link>
		<dc:creator>TumuTanzi</dc:creator>
		<pubDate>Sat, 17 Sep 2011 17:07:43 +0000</pubDate>
		<guid isPermaLink="false">http://kennethjorgensen.com/blog/?p=132#comment-100</guid>
		<description>I do not think BitCoin will have a leading future.

Since there is no real value of it, it is too different from the traditional ones.</description>
		<content:encoded><![CDATA[<p>I do not think BitCoin will have a leading future.</p>
<p>Since there is no real value of it, it is too different from the traditional ones.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Planet Earth on the Desktop by darethehair</title>
		<link>http://kennethjorgensen.com/blog/2010/06/09/planet-earth-on-the-desktop/comment-page-1/#comment-11</link>
		<dc:creator>darethehair</dc:creator>
		<pubDate>Sun, 26 Sep 2010 13:36:36 +0000</pubDate>
		<guid isPermaLink="false">http://kennethjorgensen.com/blog/?p=49#comment-11</guid>
		<description>Thanks for making a nice tidy package for getting this all together!</description>
		<content:encoded><![CDATA[<p>Thanks for making a nice tidy package for getting this all together!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
