tag:blogger.com,1999:blog-28172905.post1818364293132291547..comments2024-03-03T17:53:46.947-05:00Comments on (x, why?): Happy New Years Eve 2015(x, why?)http://www.blogger.com/profile/17499160002806879025noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-28172905.post-75297392017649690072015-02-04T08:44:21.367-05:002015-02-04T08:44:21.367-05:00Orvine said...
Happy New Years Eve 2015!! Yea...Orvine said...<br /><br /> Happy New Years Eve 2015!! Yeah it was just an outstanding evening. I attended awesome NY events on this amazing eve. I was really surprised to see the huge arrangements. You know lots of other tourists also came to attend New Years Eve NY events !<br />(x, why?)https://www.blogger.com/profile/17499160002806879025noreply@blogger.comtag:blogger.com,1999:blog-28172905.post-6900456134608530112015-02-04T00:54:58.010-05:002015-02-04T00:54:58.010-05:00This comment has been removed by a blog administrator.Orvinehttps://www.blogger.com/profile/18181170000518803106noreply@blogger.comtag:blogger.com,1999:blog-28172905.post-67624440999913979172014-12-31T18:36:02.121-05:002014-12-31T18:36:02.121-05:00You got me. I had it right in my sketch and my not...You got me. I had it right in my sketch and my notes and the I screwed it up when I put it together. I even added an extra 2 that I dudnt have in the original drawing.<br /><br />It'll be fixed in the morning.<br />(x, why?)https://www.blogger.com/profile/17499160002806879025noreply@blogger.comtag:blogger.com,1999:blog-28172905.post-49981439701257370612014-12-31T12:32:27.145-05:002014-12-31T12:32:27.145-05:00I thought 2^12 is 4096, not 2048?I thought 2^12 is 4096, not 2048?xKivhttps://www.blogger.com/profile/06281209742512240856noreply@blogger.comtag:blogger.com,1999:blog-28172905.post-47899604232394358482014-12-31T12:07:24.089-05:002014-12-31T12:07:24.089-05:00Not aware of any in particular. It was one of thos...Not aware of any in particular. It was one of those things tossed around back on the old BBSes and early Internet (for me) discussions in the 90s. <br /><br />The 2038 bug came up, too, but that doesn't fit today's theme. Or maybe it does.(x, why?)https://www.blogger.com/profile/17499160002806879025noreply@blogger.comtag:blogger.com,1999:blog-28172905.post-32222115515001259692014-12-31T11:54:26.467-05:002014-12-31T11:54:26.467-05:00I'm not aware of any systems storing YYYY in a...I'm not aware of any systems storing YYYY in a 12-bit int. Maybe a PDP-8? Not to say there isn't a bitfield somewhere but that's not the one we're worried about. <br /><br />There is a <a href="http://en.wikipedia.org/wiki/Y2038" rel="nofollow">Y2038 bug</a>, regarding 31-bit overflow of time_t seconds from epoch 1970-01-01-00:00:00 UTC. We've been trying to transition C codebases to 64-bit time_t (or 64-bit throughout) for some time. (Oddly, the NTP time system rolls in 2036?) Mark your calendar for 2038-01-19-03:14:07.Bill in Bostonhttp://m.twitter.com/n1vuxnoreply@blogger.com