<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: [Best Practice] Foreach</title>
	<atom:link href="http://www.inphpwetrust.com/best-practice-foreach/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.inphpwetrust.com/best-practice-foreach/</link>
	<description>click-click, copy, click-click, paste ...</description>
	<lastBuildDate>Thu, 10 Jun 2010 15:44:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: george</title>
		<link>http://www.inphpwetrust.com/best-practice-foreach/comment-page-1/#comment-95</link>
		<dc:creator>george</dc:creator>
		<pubDate>Thu, 10 Jun 2010 15:44:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.inphpwetrust.com/?p=179#comment-95</guid>
		<description>nu mai am datele exacte de acum un am insa imi aduc aminte ca era pe un shared hosting, centOS, intel, nu mai mult de 2GHz procesorul si ram pe la 1G</description>
		<content:encoded><![CDATA[<p>nu mai am datele exacte de acum un am insa imi aduc aminte ca era pe un shared hosting, centOS, intel, nu mai mult de 2GHz procesorul si ram pe la 1G</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bullshit</title>
		<link>http://www.inphpwetrust.com/best-practice-foreach/comment-page-1/#comment-93</link>
		<dc:creator>bullshit</dc:creator>
		<pubDate>Tue, 08 Jun 2010 17:07:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.inphpwetrust.com/?p=179#comment-93</guid>
		<description>PHP 5.2.1
APC disabled
Athlon X2 1.8GHz, 2GB DDR2 800MHz (Dual Channel)

Am testat cu un array de 100, 1000, 10000 si 100000 de elemente. Rezultatele sunt identice!

Voi cu ce versiune de PHP ati testat?</description>
		<content:encoded><![CDATA[<p>PHP 5.2.1<br />
APC disabled<br />
Athlon X2 1.8GHz, 2GB DDR2 800MHz (Dual Channel)</p>
<p>Am testat cu un array de 100, 1000, 10000 si 100000 de elemente. Rezultatele sunt identice!</p>
<p>Voi cu ce versiune de PHP ati testat?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: theheartcollector</title>
		<link>http://www.inphpwetrust.com/best-practice-foreach/comment-page-1/#comment-57</link>
		<dc:creator>theheartcollector</dc:creator>
		<pubDate>Fri, 16 Oct 2009 16:12:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.inphpwetrust.com/?p=179#comment-57</guid>
		<description>Pentru simplificarea codului se preferă folosirea referinţei:

foreach($aHash as $key =&gt; &amp;$val)
{
    $val .= &quot;a&quot;;
}

Parcă citisem şi eu undeva despre măgăria asta, şi, deşi s-ar putea să spun o prostie, faptul ca un foreach se mişcă aşa de lent s-ar putea să fie o consecinţă a faptului că acesta este mult mai generic decât un for, ştiind să manipuleze iteratori implementaţi cu ajutorul SPL-ului (http://php.net/manual/en/book.spl.php)</description>
		<content:encoded><![CDATA[<p>Pentru simplificarea codului se preferă folosirea referinţei:</p>
<p>foreach($aHash as $key =&gt; &amp;$val)<br />
{<br />
    $val .= &#8220;a&#8221;;<br />
}</p>
<p>Parcă citisem şi eu undeva despre măgăria asta, şi, deşi s-ar putea să spun o prostie, faptul ca un foreach se mişcă aşa de lent s-ar putea să fie o consecinţă a faptului că acesta este mult mai generic decât un for, ştiind să manipuleze iteratori implementaţi cu ajutorul SPL-ului (<a href="http://php.net/manual/en/book.spl.php" rel="nofollow">http://php.net/manual/en/book.spl.php</a>)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: razvan</title>
		<link>http://www.inphpwetrust.com/best-practice-foreach/comment-page-1/#comment-56</link>
		<dc:creator>razvan</dc:creator>
		<pubDate>Sun, 11 Oct 2009 21:31:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.inphpwetrust.com/?p=179#comment-56</guid>
		<description>interesant rezultatul;
si eu raman tot la foreach - chiar daca ai baze de milioane de inregistrari... nu le incarci niciodata pe toate intr-un array</description>
		<content:encoded><![CDATA[<p>interesant rezultatul;<br />
si eu raman tot la foreach &#8211; chiar daca ai baze de milioane de inregistrari&#8230; nu le incarci niciodata pe toate intr-un array</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: george</title>
		<link>http://www.inphpwetrust.com/best-practice-foreach/comment-page-1/#comment-46</link>
		<dc:creator>george</dc:creator>
		<pubDate>Sat, 18 Apr 2009 20:09:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.inphpwetrust.com/?p=179#comment-46</guid>
		<description>PHP-ul este folosit nu numai la aplicatii mici, gen web site-uri, unde un foreach este tot ce ai nevoie, dar si la aplicatii gen call center-e, care de regula tin in spate baze de date cu sute de mii de clienti, si unde viteza conteaza la acesti parametrii.</description>
		<content:encoded><![CDATA[<p>PHP-ul este folosit nu numai la aplicatii mici, gen web site-uri, unde un foreach este tot ce ai nevoie, dar si la aplicatii gen call center-e, care de regula tin in spate baze de date cu sute de mii de clienti, si unde viteza conteaza la acesti parametrii.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Attila F</title>
		<link>http://www.inphpwetrust.com/best-practice-foreach/comment-page-1/#comment-45</link>
		<dc:creator>Attila F</dc:creator>
		<pubDate>Sat, 18 Apr 2009 19:31:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.inphpwetrust.com/?p=179#comment-45</guid>
		<description>Depinde. Posibil ca foreach sa aiba in el ceva mecanism de try catch si sa mearga mai incet. Insa testele astea nu is tocmai concludente. Is rare cazurile cand cineva proceseaza array-uri asa mari cat sa conteze. Eu prefer in continuare foreach pentru cod mai simplu si usor de citit.</description>
		<content:encoded><![CDATA[<p>Depinde. Posibil ca foreach sa aiba in el ceva mecanism de try catch si sa mearga mai incet. Insa testele astea nu is tocmai concludente. Is rare cazurile cand cineva proceseaza array-uri asa mari cat sa conteze. Eu prefer in continuare foreach pentru cod mai simplu si usor de citit.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: george</title>
		<link>http://www.inphpwetrust.com/best-practice-foreach/comment-page-1/#comment-33</link>
		<dc:creator>george</dc:creator>
		<pubDate>Wed, 25 Feb 2009 17:22:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.inphpwetrust.com/?p=179#comment-33</guid>
		<description>Concluzia lor era: &quot;Proof in this example shows how functionally murderous the foreach() loop can be.&quot;.

L-am testat inainte de a posta pe blog pe mai mult de 100 de elemente, si intr-adevar rezultatul este in favoarea variantei a 2-a</description>
		<content:encoded><![CDATA[<p>Concluzia lor era: &#8220;Proof in this example shows how functionally murderous the foreach() loop can be.&#8221;.</p>
<p>L-am testat inainte de a posta pe blog pe mai mult de 100 de elemente, si intr-adevar rezultatul este in favoarea variantei a 2-a</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: solomongaby</title>
		<link>http://www.inphpwetrust.com/best-practice-foreach/comment-page-1/#comment-32</link>
		<dc:creator>solomongaby</dc:creator>
		<pubDate>Wed, 25 Feb 2009 10:16:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.inphpwetrust.com/?p=179#comment-32</guid>
		<description>eu am vazut ca au ajuns la exact concluzia inversa ;)

Conclusion:

In all cases I&#039;ve found that the foreach loop is substantially faster than both the while() and for() loop procedures</description>
		<content:encoded><![CDATA[<p>eu am vazut ca au ajuns la exact concluzia inversa <img src='http://www.inphpwetrust.com/wp-content/plugins/ym_smilies/images/yahoo_wink.gif' alt='&#59;&#41; ' class='wp-smiley' width='18' height='18' title='&#59;&#41; ' /></p>
<p>Conclusion:</p>
<p>In all cases I&#8217;ve found that the foreach loop is substantially faster than both the while() and for() loop procedures</p>
]]></content:encoded>
	</item>
</channel>
</rss>
