<?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 15:07:58 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Derick Rethans' Blog: PHP lags 23 seconds]]></title>
      <guid>http://www.phpdeveloper.org/news/4643</guid>
      <link>http://www.phpdeveloper.org/news/4643</link>
      <description><![CDATA[In <a href="http://derickrethans.nl/php_lags_23_seconds.php">this new post</a> on his blog today, <i>Derick Rethans</i> points out something that might confuse some when it comes to date/time handling - a few seconds of "lag".
<p>
<quote>
<i>
Bug report #<a href="http://bugs.php.net/35958">35958</a> must have the most obscure one ever:
<p>
"strftime usually returns a string from the number of seconds since 1 jan 1970. Now, it lags and returns a string representing 23 seconds too late."
<p>
If you know what's going on though, it isn't really that weird.
</i>
</quote>
<p>
He <a href="http://derickrethans.nl/php_lags_23_seconds.php">talks about</a> the <a href="http://en.wikipedia.org/wiki/Leap_second">leap seconds</a> that have been added to keep things straight, and how that's affecting PHP's built-in date/time functionality. He also shows an example of how you can get the "more correct" time versus the normal output...]]></description>
      <pubDate>Wed, 11 Jan 2006 06:41:13 -0600</pubDate>
    </item>
  </channel>
</rss>
