Re: C99 Status - inttypes.h

[Joern Rennecke <amylaar@spamcop.net>]

[-- Attachment #1: Type: text/plain, Size: 572 bytes --]

Quoting Gerald Pfeifer <gerald@pfeifer.com>:

> On Fri, 22 Jul 2011, Joern Rennecke wrote:
>> I agree that trying to track every library there would be a maintenance
>> burden, but giving one example of a library that works is meaningful.
>> And, since GCC is still a GNU project, mentioning the status of GNU libc
>> doesn't seem that arbitrary.
>
> Can you propose a change along these lines?  I think it does make
> sense, both to be more clear on what may be a (non-)issue and to
> refer to GNU libc as a reference implementation where that makes
> sense.

Attached.


[-- Attachment #2: c99-supp-doc-lib --]
[-- Type: text/plain, Size: 1405 bytes --]

Index: c99status.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/c99status.html,v
retrieving revision 1.57
diff -p -r1.57 c99status.html
*** c99status.html	18 Mar 2011 17:47:35 -0000	1.57
--- c99status.html	25 Sep 2011 12:15:59 -0000
*************** href="http://www.open-std.org/jtc1/sc22/
*** 13,19 ****
  (E), ISO/IEC 9899:1999/Cor.2:2004 (E) and ISO/IEC 9899:1999/Cor.3:2007
  (E)).</p>
  
! <p>Where "Library Issue" is listed in conjunction with some other
  status, this means that some compiler support is needed for the
  library support, or desirable in conjunction with it.  Note that the
  headers required of conforming freestanding implementations (clause 4
--- 13,23 ----
  (E), ISO/IEC 9899:1999/Cor.2:2004 (E) and ISO/IEC 9899:1999/Cor.3:2007
  (E)).</p>
  
! <p>"Library Issue" means that support may or may not be available depending
! on the C library used; for example, the GNU C library supports all C99
! features, provided _ISOC99_SOURCE and/or _GNU_SOURCE is defined in the
! source code or with a -D preprocessor flag.
! Where "Library Issue" is listed in conjunction with some other
  status, this means that some compiler support is needed for the
  library support, or desirable in conjunction with it.  Note that the
  headers required of conforming freestanding implementations (clause 4