<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Sun, 19 May 2013 18:26:28 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Paul Jones' Blog: Fluent Interfaces Require Fluent Situations]]></title>
      <guid>http://www.phpdeveloper.org/news/4580</guid>
      <link>http://www.phpdeveloper.org/news/4580</link>
      <description><![CDATA[On <i>Paul Jones'</i> blog today, he talks about something that's coming up <a href="http://www.mikenaberezny.com/archives/35">more and more</a> (and has especially been mentioned in PHp with all of the new frameworks popping up) - <a href="http://paul-m-jones.com/blog/?p=188">fluent interfaces</a>.
<p>
<quote>
<i>
My friend and coworker <a href="http://www.mikenaberezny.com/">Mike Naberezny</a> wrote recently of <a href="http://www.mikenaberezny.com/archives/35">fluent interfaces</a> (a.k.a. object chaining). The idea is that the fluent interface makes it very easy to read the resulting code in a way that flows naturally. This is cool, but I want to add a caveat to his examples.
<p>
I think, for a fluent interface to be effective, you need situations where you actually have all that information at one time so that you can chain the methods in a fluid way.
</i>
</quote>
<p>
<i>Paul</i> <a href="http://paul-m-jones.com/blog/?p=188">continues</a>, talking about that "something more" that might be needed to get this kind of thing working in PHP - the need to have all of the information that's going to be chained at once.]]></description>
      <pubDate>Fri, 30 Dec 2005 06:51:41 -0600</pubDate>
    </item>
  </channel>
</rss>
