<?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 for Guillermo, out of repose</title> <atom:link href="http://www.outofrepose.com/comments/feed/" rel="self" type="application/rss+xml" /><link>http://www.outofrepose.com</link> <description>The blog of a web developer, writer, and graphic designer named Guillermo A. Fisher.</description> <lastBuildDate>Fri, 27 Jan 2012 19:03:46 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <item><title>Comment on Add Relative Links to WordPress Menus by Guillermo A. Fisher</title><link>http://www.outofrepose.com/2011/05/25/add-relative-links-to-wordpress-menus/comment-page-1/#comment-1420</link> <dc:creator>Guillermo A. Fisher</dc:creator> <pubDate>Fri, 27 Jan 2012 19:03:46 +0000</pubDate> <guid
isPermaLink="false">http://www.outofrepose.com/?p=735#comment-1420</guid> <description>I&#039;m usually able to remove the &quot;http://&quot; it prepends right from the Menus screen. Is it not letting you do that?</description> <content:encoded><![CDATA[<p>I’m usually able to remove the “http://” it prepends right from the Menus screen. Is it not letting you do that?</p> ]]></content:encoded> </item> <item><title>Comment on Add Relative Links to WordPress Menus by Jan</title><link>http://www.outofrepose.com/2011/05/25/add-relative-links-to-wordpress-menus/comment-page-1/#comment-1416</link> <dc:creator>Jan</dc:creator> <pubDate>Sat, 17 Dec 2011 18:51:33 +0000</pubDate> <guid
isPermaLink="false">http://www.outofrepose.com/?p=735#comment-1416</guid> <description>It also destroys Umlauts in the current menu.</description> <content:encoded><![CDATA[<p>It also destroys Umlauts in the current menu.</p> ]]></content:encoded> </item> <item><title>Comment on Add Relative Links to WordPress Menus by Jan</title><link>http://www.outofrepose.com/2011/05/25/add-relative-links-to-wordpress-menus/comment-page-1/#comment-1415</link> <dc:creator>Jan</dc:creator> <pubDate>Sat, 17 Dec 2011 18:49:56 +0000</pubDate> <guid
isPermaLink="false">http://www.outofrepose.com/?p=735#comment-1415</guid> <description>WP automatically prepends &#039;http://&#039; to all custom links if they don&#039;t allready have it. That&#039;s why your code is not working for me.</description> <content:encoded><![CDATA[<p>WP automatically prepends ‘http://’ to all custom links if they don’t allready have it. That’s why your code is not working for me.</p> ]]></content:encoded> </item> <item><title>Comment on Extending CodeIgniter’s Exceptions Class by Guillermo A. Fisher</title><link>http://www.outofrepose.com/2010/02/17/extending-codeigniters-exceptions-class/comment-page-1/#comment-1313</link> <dc:creator>Guillermo A. Fisher</dc:creator> <pubDate>Wed, 17 Aug 2011 15:14:40 +0000</pubDate> <guid
isPermaLink="false">http://www.outofrepose.com/?p=449#comment-1313</guid> <description>@Philip The naming is a bit misleading. CodeIgniter -- at least, as it exists today -- doesn&#039;t throw exceptions. And &lt;code&gt;CI_Exceptions&lt;/code&gt; handles errors, not exceptions. You can&#039;t throw an instance of &lt;code&gt;CI_Exceptions&lt;/code&gt; (it doesn&#039;t extend PHP&#039;s native &lt;code&gt;Exception&lt;/code&gt; class, and the constructor doesn&#039;t take any arguments). If you throw an uncaught exception, &lt;code&gt;CI_Exceptions&lt;/code&gt; won&#039;t handle it. You can probably use &lt;code&gt;CI_Exceptions&lt;/code&gt; as your exception handler, although I&#039;m not sure of the nuance involved in doing that (I should try it and do a post, probably).
If you look in CodeIgniter.php, you&#039;ll find &lt;code&gt;set_error_handler(&#039;_exception_handler&#039;);&lt;/code&gt;, which begs the question, &quot;Why aren&#039;t they using &lt;a href=&quot;http://ru2.php.net/manual/en/function.set-exception-handler.php&quot; rel=&quot;nofollow&quot;&gt;&lt;code&gt;set_exception_handler()&lt;/code&gt;&lt;/a&gt; instead since the name of the callback is, um, &lt;code&gt;_exception_handler&lt;/code&gt;?&quot;. For some reason, they use the terms &quot;exception&quot; and &quot;error&quot; as if the two are interchangeable when they really aren&#039;t in PHP. &lt;code&gt;_exception_handler()&lt;/code&gt; loads &lt;code&gt;CI_Exceptions&lt;/code&gt; and uses it&#039;s methods to show and log the error. My guess is that since CI has been in development since around 2006 -- back when lots of people were still using PHP4 (&lt;code&gt;set_exception_handler()&lt;/code&gt; has only been available since PHP5) -- that&#039;s how they decided to introduce the concept of exception handling.</description> <content:encoded><![CDATA[<p>@Philip The naming is a bit misleading. CodeIgniter — at least, as it exists today — doesn’t throw exceptions. And <code>CI_Exceptions</code> handles errors, not exceptions. You can’t throw an instance of <code>CI_Exceptions</code> (it doesn’t extend PHP’s native <code>Exception</code> class, and the constructor doesn’t take any arguments). If you throw an uncaught exception, <code>CI_Exceptions</code> won’t handle it. You can probably use <code>CI_Exceptions</code> as your exception handler, although I’m not sure of the nuance involved in doing that (I should try it and do a post, probably).</p><p>If you look in CodeIgniter.php, you’ll find <code>set_error_handler('_exception_handler');</code>, which begs the question, “Why aren’t they using <a
href="http://ru2.php.net/manual/en/function.set-exception-handler.php" rel="nofollow"><code>set_exception_handler()</code></a> instead since the name of the callback is, um, <code>_exception_handler</code>?”. For some reason, they use the terms “exception” and “error” as if the two are interchangeable when they really aren’t in PHP. <code>_exception_handler()</code> loads <code>CI_Exceptions</code> and uses it’s methods to show and log the error. My guess is that since CI has been in development since around 2006 — back when lots of people were still using PHP4 (<code>set_exception_handler()</code> has only been available since PHP5) — that’s how they decided to introduce the concept of exception handling.</p> ]]></content:encoded> </item> <item><title>Comment on Extending CodeIgniter’s Exceptions Class by Philip</title><link>http://www.outofrepose.com/2010/02/17/extending-codeigniters-exceptions-class/comment-page-1/#comment-1312</link> <dc:creator>Philip</dc:creator> <pubDate>Wed, 17 Aug 2011 14:17:38 +0000</pubDate> <guid
isPermaLink="false">http://www.outofrepose.com/?p=449#comment-1312</guid> <description>I&#039;ve just started working with CodeIgniter to get started with a more structured Framework.  We had created our own, but with bring on new talent, we need something that others have worked with before.  Anyway, in my previous code I used try/catch for exceptions a lot.  Is this available in CI?  With the Framework, is there anything to catch?  I know that I could throw my own exceptions, but is the CI_Exceptions a traditional try/catch exception handler?  I guess I&#039;m a little thrown by the wording of an Exception that doesn&#039;t use try/catch, or does it?  Any additional information would be helpful.  Thanks in advance.</description> <content:encoded><![CDATA[<p>I’ve just started working with CodeIgniter to get started with a more structured Framework.  We had created our own, but with bring on new talent, we need something that others have worked with before.  Anyway, in my previous code I used try/catch for exceptions a lot.  Is this available in CI?  With the Framework, is there anything to catch?  I know that I could throw my own exceptions, but is the CI_Exceptions a traditional try/catch exception handler?  I guess I’m a little thrown by the wording of an Exception that doesn’t use try/catch, or does it?  Any additional information would be helpful.  Thanks in advance.</p> ]]></content:encoded> </item> <item><title>Comment on Debugging Data in PHP by Abou Kone</title><link>http://www.outofrepose.com/2011/07/06/debugging-data-in-php/comment-page-1/#comment-1253</link> <dc:creator>Abou Kone</dc:creator> <pubDate>Fri, 29 Jul 2011 12:45:00 +0000</pubDate> <guid
isPermaLink="false">http://www.outofrepose.com/?p=740#comment-1253</guid> <description>I am gonna snatch this one here for my CakePHP debuggings! Thanks in advance!</description> <content:encoded><![CDATA[<p>I am gonna snatch this one here for my CakePHP debuggings! Thanks in advance!</p> ]]></content:encoded> </item> <item><title>Comment on from whence they came by Guillermo A. Fisher</title><link>http://www.outofrepose.com/2011/04/08/from-whence-they-came/comment-page-1/#comment-1248</link> <dc:creator>Guillermo A. Fisher</dc:creator> <pubDate>Fri, 29 Jul 2011 00:13:54 +0000</pubDate> <guid
isPermaLink="false">http://www.outofrepose.com/?p=728#comment-1248</guid> <description>That really means a lot to me. Yes, it was &quot;The Silentfusion Collective Presents&quot; way back when, and there were several other writers involved. Now it&#039;s just me writing whenever my courage, time, and stamina line up.
Thanks again!</description> <content:encoded><![CDATA[<p>That really means a lot to me. Yes, it was “The Silentfusion Collective Presents” way back when, and there were several other writers involved. Now it’s just me writing whenever my courage, time, and stamina line up.</p><p>Thanks again!</p> ]]></content:encoded> </item> <item><title>Comment on from whence they came by Wanderer</title><link>http://www.outofrepose.com/2011/04/08/from-whence-they-came/comment-page-1/#comment-1247</link> <dc:creator>Wanderer</dc:creator> <pubDate>Thu, 28 Jul 2011 23:56:34 +0000</pubDate> <guid
isPermaLink="false">http://www.outofrepose.com/?p=728#comment-1247</guid> <description>I used to read your blog (or it might have been a collective of some sort?) a lifetime ago. It had a dark ornate arabesque design, as I recall, and I much enjoyed the content. Somehow your name was unearthed from my subconscious this evening and I naturally googled it. Good to see you&#039;re still sort of at it. :) Stay strong.</description> <content:encoded><![CDATA[<p>I used to read your blog (or it might have been a collective of some sort?) a lifetime ago. It had a dark ornate arabesque design, as I recall, and I much enjoyed the content. Somehow your name was unearthed from my subconscious this evening and I naturally googled it. Good to see you’re still sort of at it. <img
src='http://www.outofrepose.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> Stay strong.</p> ]]></content:encoded> </item> <item><title>Comment on Theme upgrade by Guillermo A. Fisher</title><link>http://www.outofrepose.com/2011/07/22/theme-upgrade/comment-page-1/#comment-1245</link> <dc:creator>Guillermo A. Fisher</dc:creator> <pubDate>Sat, 23 Jul 2011 07:03:00 +0000</pubDate> <guid
isPermaLink="false">http://www.outofrepose.com/?p=759#comment-1245</guid> <description>Thanks, sir! I may even include an actual image. The possibilities are endless.</description> <content:encoded><![CDATA[<p>Thanks, sir! I may even include an actual image. The possibilities are endless.</p> ]]></content:encoded> </item> <item><title>Comment on Theme upgrade by John C. Bland II</title><link>http://www.outofrepose.com/2011/07/22/theme-upgrade/comment-page-1/#comment-1246</link> <dc:creator>John C. Bland II</dc:creator> <pubDate>Sat, 23 Jul 2011 04:55:00 +0000</pubDate> <guid
isPermaLink="false">http://www.outofrepose.com/?p=759#comment-1246</guid> <description>Good deal.</description> <content:encoded><![CDATA[<p>Good deal.</p> ]]></content:encoded> </item> </channel> </rss>
