<?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>Tue, 21 May 2013 11:09:37 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Matthew Turland's Blog: Environmental Awareness Quickie]]></title>
      <guid>http://www.phpdeveloper.org/news/10691</guid>
      <link>http://www.phpdeveloper.org/news/10691</link>
      <description><![CDATA[<p>
<i>Matthew Turland</i> <a href="http://ishouldbecoding.com/2008/07/26/environmental-awareness-quickie">came across</a> someone having an issue running his PHP-based IRC bot (<a href="http://phergie.org/">Phergie</a>) an an environment where the <a href="http://www.php.net/exec">exec function</a> wasn't allowed:
</p>
<blockquote>
This causes a warning in the <a href="http://trac2.assembla.com/phergie/browser/trunk/Phergie/Plugin/Quit.php">Quit</a> plugin, which uses exec to automatically detection of the full path to the PHP CLI binary on non-Windows systems that it will later use that path to initiate a new PHP CLI process to "restart" the bot.
</blockquote>
<p>
It check this setting for the future, it was recommended that he look at the <a href="http://us3.php.net/manual/en/language.oop5.reflection.php#language.oop5.reflection.reflectionfunction">SPL ReflectionFunction class</a> (a part of the Standard PHP Library) that would let him check the disabled status of any PHP function (looking at the result of the isDisabled call).
</p>]]></description>
      <pubDate>Mon, 28 Jul 2008 07:57:00 -0500</pubDate>
    </item>
  </channel>
</rss>
