From owner-cvs-include  Mon Mar 31 20:02:56 1997
Return-Path: <owner-cvs-include>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id UAA06374
          for cvs-include-outgoing; Mon, 31 Mar 1997 20:02:56 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA06347;
          Mon, 31 Mar 1997 20:02:19 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id NAA03631; Tue, 1 Apr 1997 13:59:22 +1000
Date: Tue, 1 Apr 1997 13:59:22 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199704010359.NAA03631@godzilla.zeta.org.au>
To: bde@zeta.org.au, jb@cimlogic.com.au
Subject: Re: cvs commit: src/include unistd.h
Cc: cvs-all@freefall.freebsd.org, CVS-committers@freefall.freebsd.org,
        cvs-include@freefall.freebsd.org, peter@freefall.freebsd.org,
        peter@spinner.dialix.com
Sender: owner-cvs-include@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>> glibc is more careful about this.  It declares getopt stuff if
>> __USE_POSIX2 is defined.  __USE_POSIX2 is defined if
>> 
>> 	defined _POSIX_C_SOURCE >= 2 || defined _XOPEN_SOURCE
        ^^^^^^^ editing error (was superfluous `defined _POSIX_C_SOURCE &&'
>> 

>This doesn't comply with POSIX 1003.1b (and I assume .c). For POSIX 1003.1b,
>the _POSIX_C_SOURCE feature test is supposed to be compared against 199309L.
>And for 1003.1c, I guess that it is supposed to be 1996XXL where XX is the
>month that the update was (finally) published.

glibc attempts to support POSIX.1b 1993 stuff, but it (glibc-2.0 at
least) seems to assume that POSIX.1b contains POSIX.2.  Is this wrong?
A POSIX.2 draft rationale says that "each new value [of _POSIX_C_SOURCE
is expected to reserve] the name space for that new standard or revision,
plus all earlier POSIX standards".

Bruce