<?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: A Few Tips for Writing Useful Libraries in PHP</title>
	<atom:link href="http://laughingmeme.org/2003/08/05/a-few-tips-for-writing-useful-libraries-in-php/feed/" rel="self" type="application/rss+xml" />
	<link>http://laughingmeme.org/2003/08/05/a-few-tips-for-writing-useful-libraries-in-php/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Fri, 18 May 2012 17:48:27 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: chrisnof</title>
		<link>http://laughingmeme.org/2003/08/05/a-few-tips-for-writing-useful-libraries-in-php/comment-page-1/#comment-843207</link>
		<dc:creator>chrisnof</dc:creator>
		<pubDate>Fri, 28 May 2010 10:20:19 +0000</pubDate>
		<guid isPermaLink="false">http://lm.quxx.info/?p=547#comment-843207</guid>
		<description>&lt;p&gt;Nice article,
But please, fix all those &lt;i&gt; tags in your article, it makes it difficult to read..&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Nice article,
But please, fix all those <i> tags in your article, it makes it difficult to read..</i></p>]]></content:encoded>
	</item>
	<item>
		<title>By: michael</title>
		<link>http://laughingmeme.org/2003/08/05/a-few-tips-for-writing-useful-libraries-in-php/comment-page-1/#comment-823198</link>
		<dc:creator>michael</dc:creator>
		<pubDate>Tue, 23 Mar 2010 08:47:04 +0000</pubDate>
		<guid isPermaLink="false">http://lm.quxx.info/?p=547#comment-823198</guid>
		<description>&lt;p&gt;Great! I&#039;m trying to write my own libaraies , this article is a good summary!&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Great! I&#8217;m trying to write my own libaraies , this article is a good summary!</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Cesar Gonzalez</title>
		<link>http://laughingmeme.org/2003/08/05/a-few-tips-for-writing-useful-libraries-in-php/comment-page-1/#comment-798334</link>
		<dc:creator>Cesar Gonzalez</dc:creator>
		<pubDate>Mon, 09 Nov 2009 00:28:13 +0000</pubDate>
		<guid isPermaLink="false">http://lm.quxx.info/?p=547#comment-798334</guid>
		<description>&lt;p&gt;Hey Kellan, thanks for your wonderful page of tips on writing PHP libraries!  I&#039;m working on my first one, and you&#039;ve given me some good ideas on how to start and what to avoid.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Hey Kellan, thanks for your wonderful page of tips on writing PHP libraries!  I&#8217;m working on my first one, and you&#8217;ve given me some good ideas on how to start and what to avoid.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: I wish I was a better programmer... @ a.Tidwell blog</title>
		<link>http://laughingmeme.org/2003/08/05/a-few-tips-for-writing-useful-libraries-in-php/comment-page-1/#comment-45076</link>
		<dc:creator>I wish I was a better programmer... @ a.Tidwell blog</dc:creator>
		<pubDate>Wed, 16 May 2007 14:53:54 +0000</pubDate>
		<guid isPermaLink="false">http://lm.quxx.info/?p=547#comment-45076</guid>
		<description>&lt;p&gt;[...] 4. PHP is not a language that people write libraries for This mostly resonated with a blog post I read over at LaughingMeme - in which he talked (ranted?) about poor libraries written in PHP. Many PHP programmers seem to ignore writing good reusable code - inserting formatting and other erroneous material in their returns from function calls - or even worse, echoing or printing the result instead of returning it. I am guilty of this in about 99% of the code I write. I realize now, especially when taking refactoring into account, that this is time wasted and poor design. Sure, for a first pass on a complex function, why not - but when things get so complex that Iâ€™m returning formatted code (with html markup) - why the hell havenâ€™t I split it into multiple functions yet? [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] 4. PHP is not a language that people write libraries for This mostly resonated with a blog post I read over at LaughingMeme &#8211; in which he talked (ranted?) about poor libraries written in PHP. Many PHP programmers seem to ignore writing good reusable code &#8211; inserting formatting and other erroneous material in their returns from function calls &#8211; or even worse, echoing or printing the result instead of returning it. I am guilty of this in about 99% of the code I write. I realize now, especially when taking refactoring into account, that this is time wasted and poor design. Sure, for a first pass on a complex function, why not &#8211; but when things get so complex that Iâ€™m returning formatted code (with html markup) &#8211; why the hell havenâ€™t I split it into multiple functions yet? [...]</p>]]></content:encoded>
	</item>
</channel>
</rss>

