From hlj@posix.com Thu Jun 11 15:32:27 1992
Received: from netcomsv.netcom.com by dkuug.dk via EUnet with SMTP (5.64+/8+bit/IDA-1.2.8)
	id AA03624; Thu, 11 Jun 92 15:32:27 +0200
Received: from posix.COM by netcomsv.netcom.com with UUCP (4.1/SMI-4.1)
	id AA04815; Thu, 11 Jun 92 06:31:37 PDT
Received: by posix.COM (5.64/A/UX-AMR-1.0)
	id AA17828; Thu, 11 Jun 92 06:31:35 PDT
Message-Id: <9206111331.AA17828@posix.COM>
Subject: Re: (wg15tag 321) (SC22WG15.97) posix time specifications
To: sc22wg15@dkuug.dk
Date: Thu, 11 Jun 92 6:31:31 PDT
From: Hal Jespersen <hlj@posix.com>
In-Reply-To: <9206110857.AA25499@dkuug.dk>; from "Keld J|rn Simonsen" at Jun 11, 92 10:57 am
Organization: POSIX Software Group, 447 Lakeview Way, Redwood City, CA 94062
Phone: +1 (415) 364-3410	FAX: +1 (415) 364-4498
X-Mailer: ELM [version 2.2 PL0]
X-Charset: ASCII
X-Char-Esc: 29

Since this is a rather benign "bug" that doesn't affect application
portability, I propose to let it stay.  It is not an editorial change
in the IEEE sense, so I can't change it without another round of IEEE
balloting.  And, since this is there because X3J11 has it in their
standard, I would appreciate seeing some movement on their part to
correct it first.

Hal

> I have got the follwing message from Paul Eggert of Twinsun.
> Please take this into consideration when producing the DIS.
> 
> > Date: Wed, 10 Jun 92 19:06:45 PDT
> > From: eggert@twinsun.com (Paul Eggert)
> > Subject: Re: leap seconds (thanks)
> > 
> > >The POSIX.2 standard in its latest version actually allows for
> > >seconds to be in the range 0..61, so I think you should allow 
> > >this as leapseconds.  (POSIX.2 D11.3 p 380 line 4069).
> > 
> > That ``61'' is an error -- it's a bug in the C Standard,
> > most likely caused by faulty communications between
> > the U.S. Naval Observatory and the ANSI C committe.
> > 
> > The range should be ``0..60''.  Two leap seconds cannot occur in the
> > same minute, according to the international time standard CCIR
> > Recommendation 460-4 (1986).  (CCIR = International Radio Consultative
> > Committee)
> > 
> > Where do I write to to get this fixed?  I don't have a copy of POSIX.2.
> 
> Hereby notified (Hal!).
> 
> Keld
>