Y2K docs in the 21st century (was Re: [PATCH] perlfunc.pod grammar fixes)

2005-07-28 Thread Michael G Schwern
On Thu, Jul 28, 2005 at 02:55:10PM -0500, David Nicol wrote:
 I like the fact that the perl documentation is peppered
 with correct uses of effect as a verb.
 
 I doubt the wisdom of continuing to talk about Y2K compliance,
 here in Y2K+5.  We could talk about Y2100 compliance.

I think folks understand that Y2K is not just about the year 2000 but about
using truncated years in general and its not necessary to coin a new term.  
Same problem, different century.  Also...


 Note that the $year element is lnot simply one hundered plus the
 last two digits of the year.  By assuming that it is you will create
 non-Y2100-compliant code and guarantee your grandchildren careers
 in computer maintenance.

I can understand people in 1998 assuming 98 is the last two digits of the 
year and never bothering to look at the docs, but someone mistaking 105 as 
being one hundred plus the last two digits of the year... that seems a bit
contrived.

Possibly the best solution I've seen to this problem was the one employed
in Clinton Pierce's surprisingly well written Learn Perl In 24 Hours.
Its not a year, stop calling it that.  Its years offset from 1900.  His book
always refers to it as $year_offset or $year_off but never $year.


-- 
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern
Just call me 'Moron Sugar'.
http://www.somethingpositive.net/sp05182002.shtml


RE: Y2K docs in the 21st century (was Re: [PATCH] perlfunc.pod grammar fixes)

2005-07-28 Thread Horsley, Tom
 I doubt the wisdom of continuing to talk about Y2K compliance,
 here in Y2K+5.  We could talk about Y2100 compliance.

Actually the next crisis is the 2039 problem (which will be utterly
ignored because Y2K was such a bust :-).
 
Microsoft is no doubt licking its chops and waiting for 2039
since Windows doesn't use a 4 byte unsigned for its primary
timestamp, and therefore only Linux will have the 2039 bug.
 


Re: Y2K docs in the 21st century (was Re: [PATCH] perlfunc.pod grammar fixes)

2005-07-28 Thread Michael G Schwern
On Thu, Jul 28, 2005 at 06:58:35PM -0400, Horsley, Tom wrote:
 And therefore only Linux will have the 2039 bug.

s/Linux/Unix/  

Please let's not start confusing Linux with Unix or Redhat with Linux or 
Windows with computers on p5p, too.


-- 
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern
Just call me 'Moron Sugar'.
http://www.somethingpositive.net/sp05182002.shtml