Y2038 on PerlMonks

Replies are listed 'Best First'.
Re: Y2038 on PerlMonks by jdporter (Paladin) on Jun 04, 2012 at 21:10 UTC
Frankly, I'm not sure we're Y2K safe.	[reply]
Re^2: Y2038 on PerlMonks by thomas895 (Deacon) on Jun 05, 2012 at 00:01 UTC
Well, obviously it survived. OP: The Everything core doesn't have to use the epoch seconds for date fields. I don't know what it does use, but dates can also be represented as 20120604T165834, for example. Frankly, I think it will be okay. Heh, maybe it won't even be around anymore by then or have been replaced with something more modern. I would actually be worried if they still used this exact code then. Update: s/epoch times/epoch seconds/ && s/date calculations/date fields/ ~Thomas~ `confess( "I offer no guarantees on my code." );`	[reply] [d/l]
Re^3: Y2038 on PerlMonks by jdporter (Paladin) on Jun 05, 2012 at 02:08 UTC
Actually, most of what PerlMonks/Everything does in terms of dates, it does using database dates. After all: Everything is a (database) node.	[reply]
Re^4: Y2038 on PerlMonks by cavac (Parson) on Jun 13, 2012 at 20:42 UTC
Re: Y2038 on PerlMonks by Limbic~Region (Chancellor) on Jun 05, 2012 at 13:54 UTC
bulk88, There are a number of "easter eggs" about NodeReaper. The year plays into one of them - see if you can figure it out (it has nothing to do with 2038). Cheers - L~R	[reply]
Re^2: Y2038 on PerlMonks by yitzchak (Sexton) on Jun 10, 2012 at 08:20 UTC
It could perhaps be updated now.	[reply]


Your skill will accomplish what the force of many cannot
	PerlMonks