Xref: utzoo comp.text:2340 comp.std.internat:397
Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!amdahl!nsc!taux01!taux02!amos
From: amos@taux02.UUCP (Amos Shapir)
Newsgroups: comp.text,comp.std.internat
Subject: Re: All numeric representation of dates
Message-ID: <107@taux02.UUCP>
Date: 29 Aug 88 06:57:06 GMT
References: <1988Aug28.010835.17290@utzoo.uucp> <2882@hubcap.UUCP>
Organization: National Semiconductor (IC) Ltd, Israel Home of the 32532
Lines: 21
Hdate: 16 Elul 5748

In article <2882@hubcap.UUCP> billwolf@hubcap.clemson.edu writes:
>     Ah, I see... Tell me, do you think your odometer should present
>     the last two digits first, then some verbal representation of
>     the next-to-last two digits, followed by the remaining digits?
>
>     If not, then why should a chronometer be any different??
> [more about 24 vs. 12 hour representation]

You miss the  point: we are talking about  representation of information
for use by humans, which means it should be done the way humans are used
to do it.  Computers (and yes, programmers too) should  invest the extra
effort to present data in a form useful to their customers.

For scientific  purposes, time is  already presented in the  Julian date
system (e.g., the  time now is 2447402.78570 days). It  would be nice if
everybody used this system. Coming to  think of it, everybody should use
the binary system - it would be so much easier to program! :-)
-- 
	Amos Shapir				amos@nsc.com
National Semiconductor (Israel)
6 Maskit st. P.O.B. 3007, Herzlia 46104, Israel  Tel. +972 52 522261
34 48 E / 32 10 N			(My other cpu is a NS32532)