<?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: Pondering PHP 6</title> <atom:link href="http://matthewturland.com/2007/08/28/pondering-php-6/feed/" rel="self" type="application/rss+xml" /><link>http://matthewturland.com/2007/08/28/pondering-php-6/</link> <description></description> <lastBuildDate>Fri, 11 May 2012 20:03:11 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.2</generator> <item><title>By: harald</title><link>http://matthewturland.com/2007/08/28/pondering-php-6/comment-page-1/#comment-132</link> <dc:creator>harald</dc:creator> <pubDate>Mon, 03 Sep 2007 15:05:17 +0000</pubDate> <guid
isPermaLink="false">http://ishouldbecoding.com/2007/08/27/pondering-php-6/#comment-132</guid> <description>&lt;p&gt;i totally agree to you regarding &quot;named parameters.&quot; i&#039;ve learned to love them when using perl - it&#039;s always a problem when you have a method with more than one optional parameter. &lt;/p&gt;
&lt;p&gt;i can&#039;t follow their argumentation on messier code because on the other hand they implement labeled breaks, which in my opinion is really totally useless (at least i never missed them in my seven years of php programming experience) and really makes messier code if used a lot. &lt;/p&gt;
&lt;p&gt;on the other hand named parameters would help make the code more readable without having to look in the API documentation if you read other ones code.&lt;/p&gt;
&lt;p&gt;so i&#039;m not sure if the argumentation in the meeting notes is really what they think about this feature or if there are other - political - reasons not to implement named parameters.&lt;/p&gt;
&lt;p&gt;it reminds a bit on the discussion about namespaces. suddenly someone committed a working patch, and the discussions about whether to implement or not to implement namespaces were gone.&lt;/p&gt;
&lt;p&gt;thanks again for your article.&lt;/p&gt;</description> <content:encoded><![CDATA[<p>i totally agree to you regarding &#8220;named parameters.&#8221; i&#8217;ve learned to love them when using perl &#8211; it&#8217;s always a problem when you have a method with more than one optional parameter.</p><p>i can&#8217;t follow their argumentation on messier code because on the other hand they implement labeled breaks, which in my opinion is really totally useless (at least i never missed them in my seven years of php programming experience) and really makes messier code if used a lot.</p><p>on the other hand named parameters would help make the code more readable without having to look in the API documentation if you read other ones code.</p><p>so i&#8217;m not sure if the argumentation in the meeting notes is really what they think about this feature or if there are other &#8211; political &#8211; reasons not to implement named parameters.</p><p>it reminds a bit on the discussion about namespaces. suddenly someone committed a working patch, and the discussions about whether to implement or not to implement namespaces were gone.</p><p>thanks again for your article.</p> ]]></content:encoded> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using apc
Page Caching using disk: enhanced
Database Caching 3/10 queries in 0.027 seconds using apc

Served from: matthewturland.com @ 2012-05-17 16:55:59 -->
