[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

gnustandards ChangeLog standards.texi

From: karl
Subject: gnustandards ChangeLog standards.texi
Date: Tue, 01 Jan 2013 23:57:55 +0000

CVSROOT:        /sources/gnustandards
Module name:    gnustandards
Changes by:     karl <karl>     13/01/01 23:57:55

Modified files:
        .              : ChangeLog standards.texi 

Log message:
        update references to standards (+ typo)


Index: ChangeLog
RCS file: /sources/gnustandards/gnustandards/ChangeLog,v
retrieving revision 1.172
retrieving revision 1.173
diff -u -b -r1.172 -r1.173
--- ChangeLog   1 Jan 2013 23:49:58 -0000       1.172
+++ ChangeLog   1 Jan 2013 23:57:55 -0000       1.173
@@ -1,5 +1,14 @@
+2013-01-01  Paul Eggert  <address@hidden>
+       and Richard Stallman  <address@hidden>
+       * standards.texi (Standard C, Calling System Functions):
+       update references to C and POSIX standards.
 2013-01-01  Karl Berry  <address@hidden>
+       * standards.texi (Releases): no "the the" (report from Stefano
+       Lattarini).
        * maintain.texi (External Libraries): typos/grammar.
 2012-11-15  Karl Berry  <address@hidden>

Index: standards.texi
RCS file: /sources/gnustandards/gnustandards/standards.texi,v
retrieving revision 1.221
retrieving revision 1.222
diff -u -b -r1.221 -r1.222
--- standards.texi      26 Nov 2012 02:05:53 -0000      1.221
+++ standards.texi      1 Jan 2013 23:57:55 -0000       1.222
@@ -3,7 +3,7 @@
 @settitle GNU Coding Standards
 @c This date is automagically updated when you save this file:
address@hidden lastupdate November 25, 2012
address@hidden lastupdate January 1, 2013
 @c %**end of header
 @dircategory GNU organization
@@ -28,7 +28,7 @@
 Copyright @copyright{} 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
-2011, 2012 Free Software Foundation, Inc.
+2011, 2012, 2013 Free Software Foundation, Inc.
 Permission is granted to copy, distribute and/or modify this document
 under the terms of the GNU Free Documentation License, Version 1.3 or
@@ -411,15 +411,21 @@
 @cindex @sc{ansi} C standard
 1989 Standard C is widespread enough now that it is ok to use its
-features in new programs.  There is one exception: do not ever use the
+features in programs.  There is one exception: do not ever use the
 ``trigraph'' feature of Standard C.
-1999 Standard C is not widespread yet, so please do not require its
-features in programs.  It is ok to use its features if they are present.
+The 1999 and 2011 editions of Standard C are not fully supported
+on all platforms.  If you aim to support compilation by
+compilers other than GCC, you should not require these C
+features in your programs.  It is ok to use these features
+conditionally when the compiler supports them.
+If your program is only meant to compile with GCC, then you can
+use these features if GCC supports them, when they give substantial
 However, it is easy to support pre-standard compilers in most programs,
-so if you know how to do that, feel free.  If a program you are
-maintaining has such support, you should try to keep it working.
+so if you know how to do that, feel free.
 @cindex function prototypes
 To support pre-standard C, instead of writing function definitions in
@@ -2991,12 +2997,12 @@
 Historically, C implementations differed substantially, and many
 systems lacked a full implementation of ANSI/ISO C89.  Nowadays,
-however, very few systems lack a C89 compiler and GNU C supports
-almost all of C99.  Similarly, most systems implement POSIX.1-1993
-libraries and tools, and many have POSIX.1-2001.
+however, all practical systems have a C89 compiler and GNU C supports
+almost all of C99 and some of C11.  Similarly, most systems implement
+POSIX.1-2001 libraries and tools, and many have POSIX.1-2008.
 Hence, there is little reason to support old C or non-POSIX systems,
-and you may want to take advantage of C99 and POSIX-1.2001 to write
+and you may want to take advantage of standard C and POSIX to write
 clearer, more portable, or faster code.  You should use standard
 interfaces where possible; but if GNU extensions make your program
 more maintainable, powerful, or otherwise better, don't hesitate to
@@ -4092,7 +4098,7 @@
 @item a general description of what the package does;
address@hidden a reference to the the file @file{INSTALL}, which
address@hidden a reference to the file @file{INSTALL}, which
 should in turn contain an explanation of the installation procedure;
 @item a brief explanation of any unusual top-level directories or

reply via email to

[Prev in Thread] Current Thread [Next in Thread]