<?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 on: Time 1234567890 is coming up soon</title>
	<atom:link href="http://jens.mooseyard.com/2009/01/time-1234567890-is-coming-up-soon/feed/" rel="self" type="application/rss+xml" />
	<link>http://jens.mooseyard.com/2009/01/time-1234567890-is-coming-up-soon/</link>
	<description>Little boxes made of words, by Jens Alfke</description>
	<lastBuildDate>Sun, 14 Mar 2010 11:32:26 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Richard Matteson</title>
		<link>http://jens.mooseyard.com/2009/01/time-1234567890-is-coming-up-soon/comment-page-1/#comment-2922</link>
		<dc:creator>Richard Matteson</dc:creator>
		<pubDate>Thu, 12 Feb 2009 21:19:50 +0000</pubDate>
		<guid isPermaLink="false">http://mooseyard.com/Jens/2009/01/time-1234567890-is-coming-up-soon/#comment-2922</guid>
		<description>Whoops, I mean GMT -8...</description>
		<content:encoded><![CDATA[<p>Whoops, I mean GMT -8&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Matteson</title>
		<link>http://jens.mooseyard.com/2009/01/time-1234567890-is-coming-up-soon/comment-page-1/#comment-2921</link>
		<dc:creator>Richard Matteson</dc:creator>
		<pubDate>Thu, 12 Feb 2009 21:14:42 +0000</pubDate>
		<guid isPermaLink="false">http://mooseyard.com/Jens/2009/01/time-1234567890-is-coming-up-soon/#comment-2921</guid>
		<description>Well, perl is still using a 32 bit signed integer:

$ ## 2147483647 or 0x7fffffff
$ ## local time is PST here (GMT +8)
$ perl -e &#039;print scalar localtime(0x7fffffff).&quot;\n&quot;;&#039;
Mon Jan 18 19:14:07 2038
$ perl -e &#039;print scalar localtime(0).&quot;\n&quot;;&#039;
Wed Dec 31 16:00:00 1969
$ perl -e &#039;print scalar localtime(0x80000000).&quot;\n&quot;;&#039;
Fri Dec 13 12:45:52 1901
$ ## which is the same as -2147483648 (32 bit 2&#039;s complement)
$ perl -e &#039;print scalar localtime(-2147483648).&quot;\n&quot;;&#039;
Fri Dec 13 12:45:52 1901</description>
		<content:encoded><![CDATA[<p>Well, perl is still using a 32 bit signed integer:</p>
<p>$ ## 2147483647 or 0x7fffffff<br />
$ ## local time is PST here (GMT +8)<br />
$ perl -e &#8216;print scalar localtime(0x7fffffff).&#8221;\n&#8221;;&#8217;<br />
Mon Jan 18 19:14:07 2038<br />
$ perl -e &#8216;print scalar localtime(0).&#8221;\n&#8221;;&#8217;<br />
Wed Dec 31 16:00:00 1969<br />
$ perl -e &#8216;print scalar localtime(0x80000000).&#8221;\n&#8221;;&#8217;<br />
Fri Dec 13 12:45:52 1901<br />
$ ## which is the same as -2147483648 (32 bit 2&#8217;s complement)<br />
$ perl -e &#8216;print scalar localtime(-2147483648).&#8221;\n&#8221;;&#8217;<br />
Fri Dec 13 12:45:52 1901</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jens Alfke</title>
		<link>http://jens.mooseyard.com/2009/01/time-1234567890-is-coming-up-soon/comment-page-1/#comment-2920</link>
		<dc:creator>Jens Alfke</dc:creator>
		<pubDate>Thu, 12 Feb 2009 16:44:06 +0000</pubDate>
		<guid isPermaLink="false">http://mooseyard.com/Jens/2009/01/time-1234567890-is-coming-up-soon/#comment-2920</guid>
		<description>Duh, you&#039;re right of course, and they can&#039;t change that for compatibility reasons. But wasn&#039;t a 64-bit equivalent to that added ages ago?

(It doesn&#039;t affect me because I don&#039;t use POSIX time APIs; I either use Foundation, whose time type is &#039;double&#039;, or Java/Ruby/Python/etc. which all use 64-bit ints for time...)</description>
		<content:encoded><![CDATA[<p>Duh, you&#8217;re right of course, and they can&#8217;t change that for compatibility reasons. But wasn&#8217;t a 64-bit equivalent to that added ages ago?</p>
<p>(It doesn&#8217;t affect me because I don&#8217;t use POSIX time APIs; I either use Foundation, whose time type is &#8216;double&#8217;, or Java/Ruby/Python/etc. which all use 64-bit ints for time&#8230;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fluffy</title>
		<link>http://jens.mooseyard.com/2009/01/time-1234567890-is-coming-up-soon/comment-page-1/#comment-2919</link>
		<dc:creator>fluffy</dc:creator>
		<pubDate>Thu, 12 Feb 2009 16:07:50 +0000</pubDate>
		<guid isPermaLink="false">http://mooseyard.com/Jens/2009/01/time-1234567890-is-coming-up-soon/#comment-2919</guid>
		<description>Not true!  0x80000000 is INT_MIN - which is -2^31.  The (immediate) problem is that time_t is a signed int, not an unsigned int.</description>
		<content:encoded><![CDATA[<p>Not true!  0x80000000 is INT_MIN - which is -2^31.  The (immediate) problem is that time_t is a signed int, not an unsigned int.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jens Alfke</title>
		<link>http://jens.mooseyard.com/2009/01/time-1234567890-is-coming-up-soon/comment-page-1/#comment-2918</link>
		<dc:creator>Jens Alfke</dc:creator>
		<pubDate>Thu, 12 Feb 2009 16:01:03 +0000</pubDate>
		<guid isPermaLink="false">http://mooseyard.com/Jens/2009/01/time-1234567890-is-coming-up-soon/#comment-2918</guid>
		<description>Richard — Not 1901 certainly. The Unix epoch starts at 1/1/1970, so if anything it&#039;d roll over to that...</description>
		<content:encoded><![CDATA[<p>Richard — Not 1901 certainly. The Unix epoch starts at 1/1/1970, so if anything it&#8217;d roll over to that&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Matteson</title>
		<link>http://jens.mooseyard.com/2009/01/time-1234567890-is-coming-up-soon/comment-page-1/#comment-2912</link>
		<dc:creator>Richard Matteson</dc:creator>
		<pubDate>Thu, 12 Feb 2009 08:05:43 +0000</pubDate>
		<guid isPermaLink="false">http://mooseyard.com/Jens/2009/01/time-1234567890-is-coming-up-soon/#comment-2912</guid>
		<description>How about 2147483648 (0x80000000). Will it be
Fri Dec 13 12:45:52 1901 or
Mon Jan 18 19:14:08 2038</description>
		<content:encoded><![CDATA[<p>How about 2147483648 (0x80000000). Will it be<br />
Fri Dec 13 12:45:52 1901 or<br />
Mon Jan 18 19:14:08 2038</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jens Alfke</title>
		<link>http://jens.mooseyard.com/2009/01/time-1234567890-is-coming-up-soon/comment-page-1/#comment-2917</link>
		<dc:creator>Jens Alfke</dc:creator>
		<pubDate>Sat, 07 Feb 2009 18:10:32 +0000</pubDate>
		<guid isPermaLink="false">http://mooseyard.com/Jens/2009/01/time-1234567890-is-coming-up-soon/#comment-2917</guid>
		<description>Chris — You rock! I&#039;ll be there Friday afternoon with a bottle of champagne. I&#039;ve posted it to del.icio.us.</description>
		<content:encoded><![CDATA[<p>Chris — You rock! I&#8217;ll be there Friday afternoon with a bottle of champagne. I&#8217;ve posted it to del.icio.us.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Rowe</title>
		<link>http://jens.mooseyard.com/2009/01/time-1234567890-is-coming-up-soon/comment-page-1/#comment-2916</link>
		<dc:creator>Chris Rowe</dc:creator>
		<pubDate>Sat, 07 Feb 2009 17:45:26 +0000</pubDate>
		<guid isPermaLink="false">http://mooseyard.com/Jens/2009/01/time-1234567890-is-coming-up-soon/#comment-2916</guid>
		<description>Check out www.coolepochcountdown.com</description>
		<content:encoded><![CDATA[<p>Check out <a href="http://www.coolepochcountdown.com" rel="nofollow">http://www.coolepochcountdown.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fluffy</title>
		<link>http://jens.mooseyard.com/2009/01/time-1234567890-is-coming-up-soon/comment-page-1/#comment-2915</link>
		<dc:creator>fluffy</dc:creator>
		<pubDate>Thu, 22 Jan 2009 19:45:27 +0000</pubDate>
		<guid isPermaLink="false">http://mooseyard.com/Jens/2009/01/time-1234567890-is-coming-up-soon/#comment-2915</guid>
		<description>Bah, wake me up at Sat Nov 27 20:35:28 2032 (0x76543210).</description>
		<content:encoded><![CDATA[<p>Bah, wake me up at Sat Nov 27 20:35:28 2032 (0x76543210).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jens Alfke</title>
		<link>http://jens.mooseyard.com/2009/01/time-1234567890-is-coming-up-soon/comment-page-1/#comment-2914</link>
		<dc:creator>Jens Alfke</dc:creator>
		<pubDate>Thu, 22 Jan 2009 19:44:10 +0000</pubDate>
		<guid isPermaLink="false">http://mooseyard.com/Jens/2009/01/time-1234567890-is-coming-up-soon/#comment-2914</guid>
		<description>No, timestamps refer to absolute times. Zero is defined as midnight, 1 Jan 1970 GMT. It would be a real mess if you had to store a timezone too, especially because time zones shift around by political whims.</description>
		<content:encoded><![CDATA[<p>No, timestamps refer to absolute times. Zero is defined as midnight, 1 Jan 1970 GMT. It would be a real mess if you had to store a timezone too, especially because time zones shift around by political whims.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->