<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Debugging &#8211; stoimen&#039;s web log</title>
	<atom:link href="/tag/debugging/feed/" rel="self" type="application/rss+xml" />
	<link></link>
	<description>on web development</description>
	<lastBuildDate>Tue, 13 Feb 2018 08:18:15 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=5.0.3</generator>
	<item>
		<title>Debugging in Zend Framework</title>
		<link>/2010/04/29/debugging-in-zend-framework/</link>
		<comments>/2010/04/29/debugging-in-zend-framework/#respond</comments>
		<pubDate>Thu, 29 Apr 2010 16:20:55 +0000</pubDate>
		<dc:creator><![CDATA[Stoimen]]></dc:creator>
				<category><![CDATA[micro tutorial]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[zend framework]]></category>
		<category><![CDATA[Computer programming]]></category>
		<category><![CDATA[Computing]]></category>
		<category><![CDATA[debug]]></category>
		<category><![CDATA[Debugging]]></category>
		<category><![CDATA[PHP programming language]]></category>
		<category><![CDATA[Software engineering]]></category>

		<guid isPermaLink="false">/?p=1500</guid>
		<description><![CDATA[Perhaps &#8220;debugging&#8221; is a bit too strong. However when you&#8217;re dumping an array in PHP, you&#8217;d probably prefer the print_r or var_dump. echo '&#60;pre&#62;'; print_r($array); echo '&#60;/pre&#62;'; But did you know that in Zend Framework there&#8217;s a built in Zend_Debug? Zend_Debug::dump($array); Does pretty much the same thing!<div class='yarpp-related-rss'>

Related posts:<ol>
<li><a href="/2010/07/21/setting-up-global-cache-in-zend-framework/" rel="bookmark" title="Setting Up Global Cache in Zend Framework">Setting Up Global Cache in Zend Framework </a></li>
<li><a href="/2010/04/28/zend_datesetoptions-and-format_type-in-zend-framework-1-10-3/" rel="bookmark" title="Zend_Date::setOptions and format_type in Zend Framework 1.10.3">Zend_Date::setOptions and format_type in Zend Framework 1.10.3 </a></li>
<li><a href="/2010/04/09/secure-forms-with-zend-framework/" rel="bookmark" title="Secure Forms with Zend Framework">Secure Forms with Zend Framework </a></li>
<li><a href="/2010/06/10/json-and-zend-framework-zend_json/" rel="bookmark" title="JSON and Zend Framework? &#8211; Zend_Json">JSON and Zend Framework? &#8211; Zend_Json </a></li>
</ol>
</div>
]]></description>
				<content:encoded><![CDATA[<p>Perhaps &#8220;debugging&#8221; is a bit too strong. However when you&#8217;re dumping an array in PHP, you&#8217;d probably prefer the print_r or var_dump.</p>
<pre lang="php" escaped="true">
echo '&lt;pre&gt;';
print_r($array);
echo '&lt;/pre&gt;';
</pre>
<p>But did you know that in Zend Framework there&#8217;s a built in Zend_Debug?</p>
<pre lang="php">
Zend_Debug::dump($array);
</pre>
<p>Does pretty much the same thing!</p>
<div class='yarpp-related-rss'>
<p>Related posts:<ol>
<li><a href="/2010/07/21/setting-up-global-cache-in-zend-framework/" rel="bookmark" title="Setting Up Global Cache in Zend Framework">Setting Up Global Cache in Zend Framework </a></li>
<li><a href="/2010/04/28/zend_datesetoptions-and-format_type-in-zend-framework-1-10-3/" rel="bookmark" title="Zend_Date::setOptions and format_type in Zend Framework 1.10.3">Zend_Date::setOptions and format_type in Zend Framework 1.10.3 </a></li>
<li><a href="/2010/04/09/secure-forms-with-zend-framework/" rel="bookmark" title="Secure Forms with Zend Framework">Secure Forms with Zend Framework </a></li>
<li><a href="/2010/06/10/json-and-zend-framework-zend_json/" rel="bookmark" title="JSON and Zend Framework? &#8211; Zend_Json">JSON and Zend Framework? &#8211; Zend_Json </a></li>
</ol></p>
</div>
]]></content:encoded>
			<wfw:commentRss>/2010/04/29/debugging-in-zend-framework/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Write human readable debug info!</title>
		<link>/2010/01/10/write-human-readable-debug-info/</link>
		<comments>/2010/01/10/write-human-readable-debug-info/#respond</comments>
		<pubDate>Sun, 10 Jan 2010 08:42:21 +0000</pubDate>
		<dc:creator><![CDATA[Stoimen]]></dc:creator>
				<category><![CDATA[web development]]></category>
		<category><![CDATA[debug]]></category>
		<category><![CDATA[Debuggers]]></category>
		<category><![CDATA[Debugging]]></category>
		<category><![CDATA[Software bug]]></category>

		<guid isPermaLink="false">/?p=855</guid>
		<description><![CDATA[It&#8217;s a common begginer&#8217;s developer mistake to write some fullish debug info like &#8220;i&#8217;m in the IF&#8221;, or even worse &#8211; &#8220;test&#8221;. Of course when debugging you don&#8217;t get any aditional information. You know only that &#8211; you&#8217;re in the IF statement!? What a good news! That doesn&#8217;t tell you much, isn&#8217;t it? Another bad &#8230; <a href="/2010/01/10/write-human-readable-debug-info/" class="more-link">Continue reading <span class="screen-reader-text">Write human readable debug info!</span> <span class="meta-nav">&#8594;</span></a><div class='yarpp-related-rss'>

Related posts:<ol>
<li><a href="/2009/07/02/write-in-the-safari-javascript-console/" rel="bookmark" title="write in the Safari javascript console">write in the Safari javascript console </a></li>
<li><a href="/2012/02/09/how-to-dump-the-generated-zend_db-sql-query/" rel="bookmark" title="How to Dump the Generated Zend_Db SQL Query">How to Dump the Generated Zend_Db SQL Query </a></li>
<li><a href="/2009/07/27/jquery-debug-plugin/" rel="bookmark" title="jQuery debug plugin">jQuery debug plugin </a></li>
<li><a href="/2009/06/22/debug-javascript-on-ie6/" rel="bookmark" title="debug JavaScript on IE6">debug JavaScript on IE6 </a></li>
</ol>
</div>
]]></description>
				<content:encoded><![CDATA[<p>It&#8217;s a common begginer&#8217;s developer mistake to write some fullish debug info like <strong>&#8220;i&#8217;m in the IF&#8221;,</strong> or even worse &#8211; <strong>&#8220;test&#8221;</strong>. Of course when debugging you don&#8217;t get any aditional information. You know only that &#8211; you&#8217;re in the IF statement!? What a good news! That doesn&#8217;t tell you much, isn&#8217;t it?</p>
<p>Another bad way to debug is to dump only ids from some database table or loop index. At least write something before that, something like:</p>
<blockquote>
<pre>alert('on the: ' + index + ' happened something!');</pre>
</blockquote>
<p>that gives you more and can improve your work so much.</p>
<div class='yarpp-related-rss'>
<p>Related posts:<ol>
<li><a href="/2009/07/02/write-in-the-safari-javascript-console/" rel="bookmark" title="write in the Safari javascript console">write in the Safari javascript console </a></li>
<li><a href="/2012/02/09/how-to-dump-the-generated-zend_db-sql-query/" rel="bookmark" title="How to Dump the Generated Zend_Db SQL Query">How to Dump the Generated Zend_Db SQL Query </a></li>
<li><a href="/2009/07/27/jquery-debug-plugin/" rel="bookmark" title="jQuery debug plugin">jQuery debug plugin </a></li>
<li><a href="/2009/06/22/debug-javascript-on-ie6/" rel="bookmark" title="debug JavaScript on IE6">debug JavaScript on IE6 </a></li>
</ol></p>
</div>
]]></content:encoded>
			<wfw:commentRss>/2010/01/10/write-human-readable-debug-info/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
