<?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 04:56:32 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Derick Rethans' Blog: Five reasons why the shut-op operator (@) should be avoided]]></title>
      <guid>http://www.phpdeveloper.org/news/11672</guid>
      <link>http://www.phpdeveloper.org/news/11672</link>
      <description><![CDATA[<p>
<i>Derick Rethans</i> has posted <a href="http://derickrethans.nl/five_reasons_why_the_shutop_operator_@_should_be_avoided.php">just a few of the reasons</a> why the "shut-up operator" (the @ symbol) should be avoided at all costs in your PHP applications.
</p>
<blockquote>
The @-operator is often used to silence errors in noisy PHP functions'"functions that generate warnings that can not be easily prevented. [...] In those cases, there is no way how to check up-front whether the function call will not issue a warning when being called.
</blockquote>
<p>
There are side effects to using the operator, however, including hiding legitimate errors and making debugging that much more difficult. To back up his point, he includes four other reasons to avoid the operator's use (besides the debugging issues):
</p>
<ul>
<li>It's slow (part 1)
<li>It's slow (part 2)
<li>It's slow (part 3: It generates crappier code)
<li>Apfelstrudels were harmed (related to the strudel_token in the C code for the operator)
</ul>]]></description>
      <pubDate>Mon, 05 Jan 2009 12:09:37 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Felix Geisend&ouml;rfer's Blog: Make printing easy, using a PrintController]]></title>
      <guid>http://www.phpdeveloper.org/news/6346</guid>
      <link>http://www.phpdeveloper.org/news/6346</link>
      <description><![CDATA[<p>
On the ThinkingPHP blog today, <i>Felix Geisend&ouml;rfer</i> shows, based on some of his own personal work, <a href="http://www.thinkingphp.org/2006/09/24/make-printing-easy-using-a-printcontroller/">how to make printing simpler</a> inside of a CakePHP application.
</p>
<blockquote>
<p>
The web site I currently work on is going to be for the hotel where my step father is the manager of. One of the things that is going to be an important 'feature' for the site, is to make it printer friendly.
</p>
<p>
Since the new site has a very clean markup, I thought about simply creating an additonal style sheet for the media type "print". However, after thinking about it a little bit more today, I came to to the conclusion that I'm dealing with WYSIWYG visitors. So I decided to get a little fancier, and to create a PrintController, which would output printable versions of any site requested by /print/*
</p>
</blockquote>
<p>
He <a href="http://www.thinkingphp.org/2006/09/24/make-printing-easy-using-a-printcontroller/">gives the code</a> for the controller and for the easy to use link to go over to the "printable version" of each page, hiding the none-printable information from the browser.
</p>]]></description>
      <pubDate>Mon, 25 Sep 2006 07:41:14 -0500</pubDate>
    </item>
  </channel>
</rss>
