From owner-freebsd-hackers Sat May 31 14:35:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA14964 for hackers-outgoing; Sat, 31 May 1997 14:35:46 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA14953 for ; Sat, 31 May 1997 14:35:43 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA11723; Sat, 31 May 1997 14:33:10 -0700 From: Terry Lambert Message-Id: <199705312133.OAA11723@phaeton.artisoft.com> Subject: Re: fetch To: rewt@i-Plus.net (Troy Settle) Date: Sat, 31 May 1997 14:33:10 -0700 (MST) Cc: brian@awfulhak.org, terry@lambert.org, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199705312112.RAA02809@radford.i-plus.net> from "Troy Settle" at May 31, 97 05:13:51 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Why not treat a 2 digit year as a year in the current century? no > y2k problem. no y3k problem, etc.. That's actually *why* there is a year 2k problem. Say I want to schedule a conference in 2001... > Really though, a 2 digit year is just a lazy way of writing the date. > It's human readable, but is a pain for software to interpret > correctly. There's no reason for any software to use a 2 digit year > except for formatted user input/output. That's because we have the context in the huge amount of text which accompanies the date to know if it is something that has been scheduled to occur, or something which has already occurred. I would prefer that it be treated as a counting value, that is, N digits is the same as 0 followed by N-1 digits, for this reason. If you awnt the date represented correctly, why then use the correct number of digits. For people ho don't care about "19xx" vs. "20xx", they should equally not care about "00xx". Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.