[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/prep/standards index.html standards.dvi.gz ...
|
From: |
Karl Berry |
|
Subject: |
www/prep/standards index.html standards.dvi.gz ... |
|
Date: |
Sun, 11 Mar 2012 00:27:52 +0000 |
CVSROOT: /web/www
Module name: www
Changes by: Karl Berry <karl> 12/03/11 00:27:51
Modified files:
prep/standards : index.html standards.dvi.gz standards.html
standards.html.gz standards.html_node.tar.gz
standards.info.tar.gz standards.pdf
standards.ps.gz standards.texi.tar.gz
standards.txt standards.txt.gz
prep/standards/html_node: CPU-Portability.html
Change-Log-Concepts.html
Change-Logs.html Character-Set.html
Command-Variables.html
Command_002dLine-Interfaces.html
Comments.html Compatibility.html
Conditional-Changes.html
Conditional-Compilation.html
Configuration.html Contributions.html
DESTDIR.html Design-Advice.html
Directory-Variables.html
Doc-Strings-and-Manuals.html
Documentation.html
Dynamic-Plug_002dIn-Interfaces.html
Errors.html File-Usage.html
Formatting.html
GNU-Free-Documentation-License.html
GNU-Manuals.html
Graphical-Interfaces.html Index.html
Indicating-the-Part-Changed.html
Install-Command-Categories.html
Internationalization.html
Legal-Issues.html Libraries.html
License-for-Manuals.html
Makefile-Basics.html
Makefile-Conventions.html
Man-Pages.html Managing-Releases.html
Manual-Credits.html
Manual-Structure-Details.html
Memory-Usage.html Mmap.html
NEWS-File.html Names.html
Non_002dGNU-Standards.html
OID-Allocations.html Option-Table.html
Preface.html Printed-Manuals.html
Program-Behavior.html
Quote-Characters.html
Reading-Non_002dFree-Code.html
Reading-other-Manuals.html
References.html Releases.html
Semantics.html Simple-Changes.html
Source-Language.html Standard-C.html
Standard-Targets.html
Style-of-Change-Logs.html
Syntactic-Conventions.html
System-Functions.html
System-Portability.html
Trademarks.html User-Interfaces.html
Using-Extensions.html
Utilities-in-Makefiles.html
Writing-C.html _002d_002dhelp.html
_002d_002dversion.html index.html
Log message:
typo
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/index.html?cvsroot=www&r1=1.66&r2=1.67
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/standards.dvi.gz?cvsroot=www&rev=1.62
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/standards.html?cvsroot=www&r1=1.62&r2=1.63
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/standards.html.gz?cvsroot=www&rev=1.63
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/standards.html_node.tar.gz?cvsroot=www&rev=1.63
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/standards.info.tar.gz?cvsroot=www&rev=1.62
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/standards.pdf?cvsroot=www&rev=1.62
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/standards.ps.gz?cvsroot=www&rev=1.62
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/standards.texi.tar.gz?cvsroot=www&rev=1.62
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/standards.txt?cvsroot=www&r1=1.60&r2=1.61
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/standards.txt.gz?cvsroot=www&rev=1.62
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/CPU-Portability.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Change-Log-Concepts.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Change-Logs.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Character-Set.html?cvsroot=www&r1=1.44&r2=1.45
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Command-Variables.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Command_002dLine-Interfaces.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Comments.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Compatibility.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Conditional-Changes.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Conditional-Compilation.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Configuration.html?cvsroot=www&r1=1.54&r2=1.55
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Contributions.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/DESTDIR.html?cvsroot=www&r1=1.41&r2=1.42
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Design-Advice.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Directory-Variables.html?cvsroot=www&r1=1.55&r2=1.56
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Doc-Strings-and-Manuals.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Documentation.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Dynamic-Plug_002dIn-Interfaces.html?cvsroot=www&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Errors.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/File-Usage.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Formatting.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/GNU-Free-Documentation-License.html?cvsroot=www&r1=1.54&r2=1.55
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/GNU-Manuals.html?cvsroot=www&r1=1.53&r2=1.54
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Graphical-Interfaces.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Index.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Indicating-the-Part-Changed.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Install-Command-Categories.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Internationalization.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Legal-Issues.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Libraries.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/License-for-Manuals.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Makefile-Basics.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Makefile-Conventions.html?cvsroot=www&r1=1.55&r2=1.56
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Man-Pages.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Managing-Releases.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Manual-Credits.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Manual-Structure-Details.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Memory-Usage.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Mmap.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/NEWS-File.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Names.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Non_002dGNU-Standards.html?cvsroot=www&r1=1.42&r2=1.43
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/OID-Allocations.html?cvsroot=www&r1=1.26&r2=1.27
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Option-Table.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Preface.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Printed-Manuals.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Program-Behavior.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Quote-Characters.html?cvsroot=www&r1=1.44&r2=1.45
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Reading-Non_002dFree-Code.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Reading-other-Manuals.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/References.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Releases.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Semantics.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Simple-Changes.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Source-Language.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Standard-C.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Standard-Targets.html?cvsroot=www&r1=1.54&r2=1.55
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Style-of-Change-Logs.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Syntactic-Conventions.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/System-Functions.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/System-Portability.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Trademarks.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/User-Interfaces.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Using-Extensions.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Utilities-in-Makefiles.html?cvsroot=www&r1=1.54&r2=1.55
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/Writing-C.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/_002d_002dhelp.html?cvsroot=www&r1=1.36&r2=1.37
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/_002d_002dversion.html?cvsroot=www&r1=1.37&r2=1.38
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/standards/html_node/index.html?cvsroot=www&r1=1.52&r2=1.53
Patches:
Index: index.html
===================================================================
RCS file: /web/www/www/prep/standards/index.html,v
retrieving revision 1.66
retrieving revision 1.67
diff -u -b -r1.66 -r1.67
--- index.html 12 Jan 2012 19:19:55 -0000 1.66
+++ index.html 11 Mar 2012 00:26:31 -0000 1.67
@@ -4,7 +4,7 @@
<h2>GNU coding standards</h2>
<address>Free Software Foundation</address>
-<address>last updated January 12, 2012</address>
+<address>last updated March 10, 2012</address>
<p>This manual (standards) is available in the following formats:</p>
Index: standards.dvi.gz
===================================================================
RCS file: /web/www/www/prep/standards/standards.dvi.gz,v
retrieving revision 1.61
retrieving revision 1.62
diff -u -b -r1.61 -r1.62
Binary files /tmp/cvsSaxXbE and /tmp/cvskmSXoJ differ
Index: standards.html
===================================================================
RCS file: /web/www/www/prep/standards/standards.html,v
retrieving revision 1.62
retrieving revision 1.63
diff -u -b -r1.62 -r1.63
--- standards.html 12 Jan 2012 19:19:56 -0000 1.62
+++ standards.html 11 Mar 2012 00:26:31 -0000 1.63
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards</title>
@@ -168,7 +168,7 @@
<a name="GNU-Coding-Standards"></a>
<h1 class="top">GNU Coding Standards</h1>
-<p>The GNU coding standards, last updated January 8, 2012.
+<p>The GNU coding standards, last updated March 8, 2012.
</p>
<p>Copyright © 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -272,7 +272,7 @@
<a
href="http://www.gnu.org/software/hello/hello.html";>http://www.gnu.org/software/hello/hello.html</a>.
</p>
<p>This release of the GNU Coding Standards was last updated
-January 8, 2012.
+March 8, 2012.
</p>
<hr>
@@ -1253,7 +1253,7 @@
each on a separate line.
</p>
<p>Next should follow a line stating the license, preferably using one of
-abbrevations below, and a brief statement that the program is free
+abbreviations below, and a brief statement that the program is free
software, and that users are free to copy and change it. Also mention
that there is no warranty, to the extent permitted by law. See
recommended wording below.
@@ -3366,10 +3366,10 @@
as <code>lint</code>, <code>clang</code>, and GCC with extra warnings
options such as ‘<samp>-Wconversion</samp>’ and
‘<samp>-Wundef</samp>’. These
tools can help find bugs and unclear code, but they can also generate
-so many false alarms that that it hurts readability to silence them
-with unnecessary casts, wrappers, and other complications. For
-example, please don’t insert casts to <code>void</code> or calls to
-do-nothing functions merely to pacify a lint checker.
+so many false alarms that it hurts readability to silence them with
+unnecessary casts, wrappers, and other complications. For example,
+please don’t insert casts to <code>void</code> or calls to do-nothing
+functions merely to pacify a lint checker.
</p>
<p>Declarations of external functions and functions to appear later in the
source file should all go in one place near the beginning of the file
@@ -6772,7 +6772,6 @@
to permit their use in free software.
</p>
-
<hr>
<a name="Index"></a>
<div class="header">
@@ -7097,9 +7096,8 @@
</td></tr></table>
<hr>
-<p>
-</p>
+
</body>
</html>
Index: standards.html.gz
===================================================================
RCS file: /web/www/www/prep/standards/standards.html.gz,v
retrieving revision 1.62
retrieving revision 1.63
diff -u -b -r1.62 -r1.63
Binary files /tmp/cvsrKvBIG and /tmp/cvsSWDn1L differ
Index: standards.html_node.tar.gz
===================================================================
RCS file: /web/www/www/prep/standards/standards.html_node.tar.gz,v
retrieving revision 1.62
retrieving revision 1.63
diff -u -b -r1.62 -r1.63
Binary files /tmp/cvssLEUpF and /tmp/cvsR3ShKK differ
Index: standards.info.tar.gz
===================================================================
RCS file: /web/www/www/prep/standards/standards.info.tar.gz,v
retrieving revision 1.61
retrieving revision 1.62
diff -u -b -r1.61 -r1.62
Binary files /tmp/cvsmR1PqG and /tmp/cvsJdfCML differ
Index: standards.pdf
===================================================================
RCS file: /web/www/www/prep/standards/standards.pdf,v
retrieving revision 1.61
retrieving revision 1.62
diff -u -b -r1.61 -r1.62
Binary files /tmp/cvstqRzjJ and /tmp/cvswinmIO differ
Index: standards.ps.gz
===================================================================
RCS file: /web/www/www/prep/standards/standards.ps.gz,v
retrieving revision 1.61
retrieving revision 1.62
diff -u -b -r1.61 -r1.62
Binary files /tmp/cvsJNqbNI and /tmp/cvsD0RXfO differ
Index: standards.texi.tar.gz
===================================================================
RCS file: /web/www/www/prep/standards/standards.texi.tar.gz,v
retrieving revision 1.61
retrieving revision 1.62
diff -u -b -r1.61 -r1.62
Binary files /tmp/cvsJbwHwK and /tmp/cvsQG2r1P differ
Index: standards.txt
===================================================================
RCS file: /web/www/www/prep/standards/standards.txt,v
retrieving revision 1.60
retrieving revision 1.61
diff -u -b -r1.60 -r1.61
--- standards.txt 12 Jan 2012 19:19:59 -0000 1.60
+++ standards.txt 11 Mar 2012 00:26:35 -0000 1.61
@@ -18,8 +18,8 @@
4.5 Standards for Interfaces Generally
4.6 Standards for Graphical Interfaces
4.7 Standards for Command Line Interfaces
- 4.7.1 `--version'
- 4.7.2 `--help'
+ 4.7.1 '--version'
+ 4.7.2 '--help'
4.8 Standards for Dynamic Plug-in Interfaces
4.9 Table of Long Options
4.10 OID Allocations
@@ -59,7 +59,7 @@
7.2.1 General Conventions for Makefiles
7.2.2 Utilities in Makefiles
7.2.3 Variables for Specifying Commands
- 7.2.4 `DESTDIR': Support for Staged Installs
+ 7.2.4 'DESTDIR': Support for Staged Installs
7.2.5 Variables for Installation Directories
7.2.6 Standard Targets for Users
7.2.7 Install Command Categories
@@ -70,7 +70,7 @@
GNU Coding Standards
********************
-The GNU coding standards, last updated January 8, 2012.
+The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000,
2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012
@@ -98,16 +98,16 @@
recently, please check for a newer version. You can get the GNU Coding
Standards from the GNU web server in many different formats, including
the Texinfo source, PDF, HTML, DVI, plain text, and more, at:
-`http://www.gnu.org/prep/standards/'.
+'http://www.gnu.org/prep/standards/'.
If you are maintaining an official GNU package, in addition to this
document, please read and follow the GNU maintainer information (*note
Contents: (maintain)Top.).
If you want to receive diffs for every change to these GNU documents,
-join the mailing list address@hidden', via the web
+join the mailing list 'address@hidden', via the web
interface at
-`http://lists.gnu.org/mailman/listinfo/gnustandards-commit'. Archives
+'http://lists.gnu.org/mailman/listinfo/gnustandards-commit'. Archives
are also available there.
Please send corrections or suggestions for this document to
@@ -117,7 +117,7 @@
that's difficult for you, you can make a context diff for some other
version of this document, or propose it in any way that makes it clear.
The source repository for this document can be found at
-`http://savannah.gnu.org/projects/gnustandards'.
+'http://savannah.gnu.org/projects/gnustandards'.
These standards cover the minimum of what is important when writing a
GNU package. Likely, the need for additional standards will come up.
@@ -133,9 +133,9 @@
The GNU Hello program serves as an example of how to follow the GNU
coding standards for a trivial program.
-`http://www.gnu.org/software/hello/hello.html'.
+'http://www.gnu.org/software/hello/hello.html'.
- This release of the GNU Coding Standards was last updated January 8,
+ This release of the GNU Coding Standards was last updated March 8,
2012.
2 Keeping Free Software Free
@@ -250,7 +250,7 @@
Usually we write the name "Windows" in full, but when brevity is very
important (as in file names and sometimes symbol names), we abbreviate
it to "w". For instance, the files and functions in Emacs that deal
-with Windows start with `w32'.
+with Windows start with 'w32'.
3 General Program Design
************************
@@ -293,7 +293,7 @@
pioneered this technique.
The standard extensibility interpreter for GNU software is Guile
-(`http://www.gnu.org/software/guile/'), which implements the language
+('http://www.gnu.org/software/guile/'), which implements the language
Scheme (an especially clean and simple dialect of Lisp). Guile also
includes bindings for GTK+/GNOME, making it practical to write modern
GUI functionality within Guile. We don't reject programs written in
@@ -312,22 +312,22 @@
modes for each of them.
Standard C and POSIX prohibit many kinds of extensions. Feel free to
-make the extensions anyway, and include a `--ansi', `--posix', or
-`--compatible' option to turn them off. However, if the extension has a
+make the extensions anyway, and include a '--ansi', '--posix', or
+'--compatible' option to turn them off. However, if the extension has a
significant chance of breaking any real programs or scripts, then it is
not really upward compatible. So you should try to redesign its
interface to make it upward compatible.
Many GNU programs suppress extensions that conflict with POSIX if the
-environment variable `POSIXLY_CORRECT' is defined (even if it is defined
+environment variable 'POSIXLY_CORRECT' is defined (even if it is defined
with a null value). Please make your program recognize this variable if
appropriate.
When a feature is used only by users (not by programs or command
files), and it is done poorly in Unix, feel free to replace it
completely with something totally different and better. (For example,
-`vi' is replaced with Emacs.) But it is nice to offer a compatible
-feature as well. (There is a free `vi' clone, so we offer it.)
+'vi' is replaced with Emacs.) But it is nice to offer a compatible
+feature as well. (There is a free 'vi' clone, so we offer it.)
Additional useful features are welcome regardless of whether there is
any precedent for them.
@@ -345,8 +345,8 @@
fewer kinds of machines.
With some extensions, it might be easy to provide both alternatives.
-For example, you can define functions with a "keyword" `INLINE' and
-define that as a macro to expand into either `inline' or nothing,
+For example, you can define functions with a "keyword" 'INLINE' and
+define that as a macro to expand into either 'inline' or nothing,
depending on the compiler.
In general, perhaps it is best not to use the extensions if you can
@@ -400,18 +400,18 @@
And once you have the declaration, you normally lose nothing by writing
the function definition in the pre-standard style.
- This technique does not work for integer types narrower than `int'.
-If you think of an argument as being of a type narrower than `int',
-declare it as `int' instead.
+ This technique does not work for integer types narrower than 'int'.
+If you think of an argument as being of a type narrower than 'int',
+declare it as 'int' instead.
There are a few special cases where this technique is hard to use.
For example, if a function argument needs to hold the system type
-`dev_t', you run into trouble, because `dev_t' is shorter than `int' on
-some machines; but you cannot use `int' instead, because `dev_t' is
-wider than `int' on some machines. There is no type you can safely use
+'dev_t', you run into trouble, because 'dev_t' is shorter than 'int' on
+some machines; but you cannot use 'int' instead, because 'dev_t' is
+wider than 'int' on some machines. There is no type you can safely use
on all machines in a non-standard definition. The only way to support
non-standard C and pass such an argument is to check the width of
-`dev_t' using Autoconf and choose the argument type accordingly. This
+'dev_t' using Autoconf and choose the argument type accordingly. This
may not be worth the trouble.
In order to support pre-standard compilers that do not recognize
@@ -428,7 +428,7 @@
===========================
When supporting configuration options already known when building your
-program we prefer using `if (... )' over conditional compilation, as in
+program we prefer using 'if (... )' over conditional compilation, as in
the former case the compiler is able to perform more extensive checking
of all possible code paths.
@@ -450,15 +450,15 @@
A modern compiler such as GCC will generate exactly the same code in
both cases, and we have been using similar techniques with good success
in several projects. Of course, the former method assumes that
-`HAS_FOO' is defined as either 0 or 1.
+'HAS_FOO' is defined as either 0 or 1.
While this is not a silver bullet solving all portability problems,
and is not always appropriate, following this policy would have saved
GCC developers many hours, or even days, per year.
- In the case of function-like macros like `REVERSIBLE_CC_MODE' in GCC
-which cannot be simply used in `if (...)' statements, there is an easy
-workaround. Simply introduce another macro `HAS_REVERSIBLE_CC_MODE' as
+ In the case of function-like macros like 'REVERSIBLE_CC_MODE' in GCC
+which cannot be simply used in 'if (...)' statements, there is an easy
+workaround. Simply introduce another macro 'HAS_REVERSIBLE_CC_MODE' as
in the following example:
#ifdef REVERSIBLE_CC_MODE
@@ -499,15 +499,15 @@
prohibited. How silly! GCC implements many extensions, some of which
were later adopted as part of the standard. If you want these
constructs to give an error message as "required" by the standard, you
-must specify `--pedantic', which was implemented only so that we can say
+must specify '--pedantic', which was implemented only so that we can say
"GCC is a 100% implementation of the standard", not because there is any
reason to actually use it.
- POSIX.2 specifies that `df' and `du' must output sizes by default in
+ POSIX.2 specifies that 'df' and 'du' must output sizes by default in
units of 512 bytes. What users want is units of 1k, so that is what we
do by default. If you want the ridiculous behavior "required" by POSIX,
-you must set the environment variable `POSIXLY_CORRECT' (which was
-originally going to be named `POSIX_ME_HARDER').
+you must set the environment variable 'POSIXLY_CORRECT' (which was
+originally going to be named 'POSIX_ME_HARDER').
GNU utilities also depart from the letter of the POSIX.2
specification when they support long-named command-line options, and
@@ -534,34 +534,34 @@
the most important.
Check every system call for an error return, unless you know you wish
-to ignore errors. Include the system error text (from `perror',
-`strerror', or equivalent) in _every_ error message resulting from a
+to ignore errors. Include the system error text (from 'perror',
+'strerror', or equivalent) in _every_ error message resulting from a
failing system call, as well as the name of the file if any and the name
of the utility. Just "cannot open foo.c" or "stat failed" is not
sufficient.
- Check every call to `malloc' or `realloc' to see if it returned zero.
-Check `realloc' even if you are making the block smaller; in a system
-that rounds block sizes to a power of 2, `realloc' may get a different
+ Check every call to 'malloc' or 'realloc' to see if it returned zero.
+Check 'realloc' even if you are making the block smaller; in a system
+that rounds block sizes to a power of 2, 'realloc' may get a different
block if you ask for less space.
- In Unix, `realloc' can destroy the storage block if it returns zero.
-GNU `realloc' does not have this bug: if it fails, the original block is
+ In Unix, 'realloc' can destroy the storage block if it returns zero.
+GNU 'realloc' does not have this bug: if it fails, the original block is
unchanged. Feel free to assume the bug is fixed. If you wish to run
your program on Unix, and wish to avoid lossage in this case, you can
-use the GNU `malloc'.
+use the GNU 'malloc'.
- You must expect `free' to alter the contents of the block that was
+ You must expect 'free' to alter the contents of the block that was
freed. Anything you want to fetch from the block, you must fetch before
-calling `free'.
+calling 'free'.
- If `malloc' fails in a noninteractive program, make that a fatal
+ If 'malloc' fails in a noninteractive program, make that a fatal
error. In an interactive program (one that reads commands from the
user), it is better to abort the command and return to the command
reader loop. This allows the user to kill other processes to free up
virtual memory, and then try the command again.
- Use `getopt_long' to decode arguments, unless the argument syntax
+ Use 'getopt_long' to decode arguments, unless the argument syntax
makes this unreasonable.
When static storage is to be written in during program execution, use
@@ -571,18 +571,18 @@
Try to avoid low-level interfaces to obscure Unix data structures
(such as file directories, utmp, or the layout of kernel memory), since
these are less likely to work compatibly. If you need to find all the
-files in a directory, use `readdir' or some other high-level interface.
+files in a directory, use 'readdir' or some other high-level interface.
These are supported compatibly by GNU.
The preferred signal handling facilities are the BSD variant of
-`signal', and the POSIX `sigaction' function; the alternative USG
-`signal' interface is an inferior design.
+'signal', and the POSIX 'sigaction' function; the alternative USG
+'signal' interface is an inferior design.
Nowadays, using the POSIX signal functions may be the easiest way to
-make a program portable. If you use `signal', then on GNU/Linux systems
-running GNU libc version 1, you should include `bsd/signal.h' instead of
-`signal.h', so as to get BSD behavior. It is up to you whether to
-support systems where `signal' has only the USG behavior, or give up on
+make a program portable. If you use 'signal', then on GNU/Linux systems
+running GNU libc version 1, you should include 'bsd/signal.h' instead of
+'signal.h', so as to get BSD behavior. It is up to you whether to
+support systems where 'signal' has only the USG behavior, or give up on
them.
In error checks that detect "impossible" conditions, just abort.
@@ -599,9 +599,9 @@
try to return 256 as the exit status, the parent process will see 0 as
the status, and it will appear that the program succeeded.
- If you make temporary files, check the `TMPDIR' environment variable;
+ If you make temporary files, check the 'TMPDIR' environment variable;
if that variable is defined, use the specified directory instead of
-`/tmp'.
+'/tmp'.
In addition, be aware that there is a possible security problem when
creating temporary files in world-writable directories. In C, you can
@@ -609,11 +609,11 @@
fd = open (filename, O_WRONLY | O_CREAT | O_EXCL, 0600);
-or by using the `mkstemps' function from Gnulib (*note
+or by using the 'mkstemps' function from Gnulib (*note
(gnulib)mkstemps::).
- In bash, use `set -C' (long name `noclobber') to avoid this problem.
-In addition, the `mktemp' utility is a more general solution for
+ In bash, use 'set -C' (long name 'noclobber') to avoid this problem.
+In addition, the 'mktemp' utility is a more general solution for
creating temporary files from shell scripts (*note (coreutils)mktemp
invocation::).
@@ -622,7 +622,7 @@
Try to make library functions reentrant. If they need to do dynamic
storage allocation, at least try to avoid any nonreentrancy aside from
-that of `malloc' itself.
+that of 'malloc' itself.
Here are certain name conventions for libraries, to avoid name
conflicts.
@@ -637,7 +637,7 @@
then they can both go in the same file.
External symbols that are not documented entry points for the user
-should have names beginning with `_'. The `_' should be followed by the
+should have names beginning with '_'. The '_' should be followed by the
chosen name prefix for the library, to prevent collisions with other
libraries. These can go in the same files with user entry points if you
like.
@@ -663,7 +663,7 @@
numbers assuming that space and all ASCII printing characters have equal
width, and assuming tab stops every 8 columns. For non-ASCII
characters, Unicode character widths should be used when in a UTF-8
-locale; GNU libc and GNU gnulib provide suitable `wcwidth' functions.
+locale; GNU libc and GNU gnulib provide suitable 'wcwidth' functions.
The error message can also give both the starting and ending
positions of the erroneous text. There are several formats so that you
@@ -733,11 +733,11 @@
behavior.
Compatibility requires certain programs to depend on the type of
-output device. It would be disastrous if `ls' or `sh' did not do so in
+output device. It would be disastrous if 'ls' or 'sh' did not do so in
the way all users expect. In some of these cases, we supplement the
program with a preferred alternate version that does not depend on the
-output device type. For example, we provide a `dir' program much like
-`ls' except that its default output format is always multi-column
+output device type. For example, we provide a 'dir' program much like
+'ls' except that its default output format is always multi-column
format.
4.6 Standards for Graphical Interfaces
@@ -765,40 +765,40 @@
=========================================
It is a good idea to follow the POSIX guidelines for the command-line
-options of a program. The easiest way to do this is to use `getopt' to
-parse them. Note that the GNU version of `getopt' will normally permit
-options anywhere among the arguments unless the special argument `--' is
+options of a program. The easiest way to do this is to use 'getopt' to
+parse them. Note that the GNU version of 'getopt' will normally permit
+options anywhere among the arguments unless the special argument '--' is
used. This is not what POSIX specifies; it is a GNU extension.
Please define long-named options that are equivalent to the
single-letter Unix-style options. We hope to make GNU more user
friendly this way. This is easy to do with the GNU function
-`getopt_long'.
+'getopt_long'.
One of the advantages of long-named options is that they can be
consistent from program to program. For example, users should be able
to expect the "verbose" option of any GNU program which has one, to be
-spelled precisely `--verbose'. To achieve this uniformity, look at the
+spelled precisely '--verbose'. To achieve this uniformity, look at the
table of common long-option names when you choose the option names for
your program (*note Option Table::).
It is usually a good idea for file names given as ordinary arguments
to be input files only; any output files would be specified using
-options (preferably `-o' or `--output'). Even if you allow an output
+options (preferably '-o' or '--output'). Even if you allow an output
file name as an ordinary argument for compatibility, try to provide an
option as another way to specify it. This will lead to more consistency
among GNU utilities, and fewer idiosyncrasies for users to remember.
- All programs should support two standard options: `--version' and
-`--help'. CGI programs should accept these as command-line options, and
-also if given as the `PATH_INFO'; for instance, visiting
-`http://example.org/p.cgi/--help' in a browser should output the same
-information as invoking `p.cgi --help' from the command line.
+ All programs should support two standard options: '--version' and
+'--help'. CGI programs should accept these as command-line options, and
+also if given as the 'PATH_INFO'; for instance, visiting
+'http://example.org/p.cgi/--help' in a browser should output the same
+information as invoking 'p.cgi --help' from the command line.
-4.7.1 `--version'
+4.7.1 '--version'
-----------------
-The standard `--version' option should direct the program to print
+The standard '--version' option should direct the program to print
information about its name, version, origin and legal status, all on
standard output, and then exit successfully. Other options and
arguments should be ignored once this is seen, and the program should
@@ -811,9 +811,9 @@
GNU Emacs 19.30
The program's name should be a constant string; _don't_ compute it from
-`argv[0]'. The idea is to state the standard or canonical name for the
+'argv[0]'. The idea is to state the standard or canonical name for the
program, not its file name. There are other ways to find out the
-precise file name where a command is found in `PATH'.
+precise file name where a command is found in 'PATH'.
If the program is a subsidiary part of a larger package, mention the
package name in parentheses, like this:
@@ -840,7 +840,7 @@
put each on a separate line.
Next should follow a line stating the license, preferably using one
-of abbrevations below, and a brief statement that the program is free
+of abbreviations below, and a brief statement that the program is free
software, and that users are free to copy and change it. Also mention
that there is no warranty, to the extent permitted by law. See
recommended wording below.
@@ -869,7 +869,7 @@
Translations of the above lines must preserve the validity of the
copyright notices (*note Internationalization::). If the translation's
-character set supports it, the `(C)' should be replaced with the
+character set supports it, the '(C)' should be replaced with the
copyright symbol, as follows:
(the official copyright symbol, which is the letter C in a circle);
@@ -880,74 +880,74 @@
have legal significance.
Finally, here is the table of our suggested license abbreviations.
-Any abbreviation can be followed by `vVERSION[+]', meaning that
-particular version, or later versions with the `+', as shown above.
+Any abbreviation can be followed by 'vVERSION[+]', meaning that
+particular version, or later versions with the '+', as shown above.
In the case of exceptions for extra permissions with the GPL, we use
-`/' for a separator; the version number can follow the license
+'/' for a separator; the version number can follow the license
abbreviation as usual, as in the examples below.
GPL
- GNU General Public License, `http://www.gnu.org/licenses/gpl.html'.
+ GNU General Public License, 'http://www.gnu.org/licenses/gpl.html'.
LGPL
GNU Lesser General Public License,
- `http://www.gnu.org/licenses/lgpl.html'.
+ 'http://www.gnu.org/licenses/lgpl.html'.
GPL/Ada
GNU GPL with the exception for Ada.
Apache
The Apache Software Foundation license,
- `http://www.apache.org/licenses'.
+ 'http://www.apache.org/licenses'.
Artistic
The Artistic license used for Perl,
- `http://www.perlfoundation.org/legal'.
+ 'http://www.perlfoundation.org/legal'.
Expat
- The Expat license, `http://www.jclark.com/xml/copying.txt'.
+ The Expat license, 'http://www.jclark.com/xml/copying.txt'.
MPL
- The Mozilla Public License, `http://www.mozilla.org/MPL/'.
+ The Mozilla Public License, 'http://www.mozilla.org/MPL/'.
OBSD
The original (4-clause) BSD license, incompatible with the GNU GPL
- `http://www.xfree86.org/3.3.6/COPYRIGHT2.html#6'.
+ 'http://www.xfree86.org/3.3.6/COPYRIGHT2.html#6'.
PHP
- The license used for PHP, `http://www.php.net/license/'.
+ The license used for PHP, 'http://www.php.net/license/'.
public domain
The non-license that is being in the public domain,
- `http://www.gnu.org/licenses/license-list.html#PublicDomain'.
+ 'http://www.gnu.org/licenses/license-list.html#PublicDomain'.
Python
- The license for Python, `http://www.python.org/2.0.1/license.html'.
+ The license for Python, 'http://www.python.org/2.0.1/license.html'.
RBSD
The revised (3-clause) BSD, compatible with the GNU GPL,
- `http://www.xfree86.org/3.3.6/COPYRIGHT2.html#5'.
+ 'http://www.xfree86.org/3.3.6/COPYRIGHT2.html#5'.
X11
The simple non-copyleft license used for most versions of the X
- Window System, `http://www.xfree86.org/3.3.6/COPYRIGHT2.html#3'.
+ Window System, 'http://www.xfree86.org/3.3.6/COPYRIGHT2.html#3'.
Zlib
- The license for Zlib, `http://www.gzip.org/zlib/zlib_license.html'.
+ The license for Zlib, 'http://www.gzip.org/zlib/zlib_license.html'.
More information about these licenses and many more are on the GNU
-licensing web pages, `http://www.gnu.org/licenses/license-list.html'.
+licensing web pages, 'http://www.gnu.org/licenses/license-list.html'.
-4.7.2 `--help'
+4.7.2 '--help'
--------------
-The standard `--help' option should output brief documentation for how
+The standard '--help' option should output brief documentation for how
to invoke the program, on standard output, then exit successfully.
Other options and arguments should be ignored once this is seen, and the
program should not perform its normal function.
- Near the end of the `--help' option's output, please place lines
+ Near the end of the '--help' option's output, please place lines
giving the email address for bug reports, the package's home page
(normally <http://www.gnu.org/software/PKG>, and the general page for
help using GNU programs. The format should be like this:
@@ -975,7 +975,7 @@
Second, you should require plug-in developers to affirm that their
plug-ins are released under an appropriate license. This should be
enforced with a simple programmatic check. For GCC, again for example,
-a plug-in must define the global symbol `plugin_is_GPL_compatible', thus
+a plug-in must define the global symbol 'plugin_is_GPL_compatible', thus
asserting that the plug-in is released under a GPL-compatible license
(*note Plugins: (gccint)Plugins.).
@@ -999,1084 +999,1084 @@
please send <address@hidden> a list of them, with their meanings,
so we can update the table.
-`after-date'
- `-N' in `tar'.
+'after-date'
+ '-N' in 'tar'.
-`all'
- `-a' in `du', `ls', `nm', `stty', `uname', and `unexpand'.
+'all'
+ '-a' in 'du', 'ls', 'nm', 'stty', 'uname', and 'unexpand'.
-`all-text'
- `-a' in `diff'.
+'all-text'
+ '-a' in 'diff'.
-`almost-all'
- `-A' in `ls'.
+'almost-all'
+ '-A' in 'ls'.
-`append'
- `-a' in `etags', `tee', `time'; `-r' in `tar'.
+'append'
+ '-a' in 'etags', 'tee', 'time'; '-r' in 'tar'.
-`archive'
- `-a' in `cp'.
+'archive'
+ '-a' in 'cp'.
-`archive-name'
- `-n' in `shar'.
+'archive-name'
+ '-n' in 'shar'.
-`arglength'
- `-l' in `m4'.
+'arglength'
+ '-l' in 'm4'.
-`ascii'
- `-a' in `diff'.
+'ascii'
+ '-a' in 'diff'.
-`assign'
- `-v' in `gawk'.
+'assign'
+ '-v' in 'gawk'.
-`assume-new'
- `-W' in `make'.
+'assume-new'
+ '-W' in 'make'.
-`assume-old'
- `-o' in `make'.
+'assume-old'
+ '-o' in 'make'.
-`auto-check'
- `-a' in `recode'.
+'auto-check'
+ '-a' in 'recode'.
-`auto-pager'
- `-a' in `wdiff'.
+'auto-pager'
+ '-a' in 'wdiff'.
-`auto-reference'
- `-A' in `ptx'.
+'auto-reference'
+ '-A' in 'ptx'.
-`avoid-wraps'
- `-n' in `wdiff'.
+'avoid-wraps'
+ '-n' in 'wdiff'.
-`background'
+'background'
For server programs, run in the background.
-`backward-search'
- `-B' in `ctags'.
+'backward-search'
+ '-B' in 'ctags'.
-`basename'
- `-f' in `shar'.
+'basename'
+ '-f' in 'shar'.
-`batch'
+'batch'
Used in GDB.
-`baud'
+'baud'
Used in GDB.
-`before'
- `-b' in `tac'.
+'before'
+ '-b' in 'tac'.
-`binary'
- `-b' in `cpio' and `diff'.
+'binary'
+ '-b' in 'cpio' and 'diff'.
-`bits-per-code'
- `-b' in `shar'.
+'bits-per-code'
+ '-b' in 'shar'.
-`block-size'
- Used in `cpio' and `tar'.
+'block-size'
+ Used in 'cpio' and 'tar'.
-`blocks'
- `-b' in `head' and `tail'.
+'blocks'
+ '-b' in 'head' and 'tail'.
-`break-file'
- `-b' in `ptx'.
+'break-file'
+ '-b' in 'ptx'.
-`brief'
+'brief'
Used in various programs to make output shorter.
-`bytes'
- `-c' in `head', `split', and `tail'.
+'bytes'
+ '-c' in 'head', 'split', and 'tail'.
-`c++'
- `-C' in `etags'.
+'c++'
+ '-C' in 'etags'.
-`catenate'
- `-A' in `tar'.
+'catenate'
+ '-A' in 'tar'.
-`cd'
+'cd'
Used in various programs to specify the directory to use.
-`changes'
- `-c' in `chgrp' and `chown'.
+'changes'
+ '-c' in 'chgrp' and 'chown'.
-`classify'
- `-F' in `ls'.
+'classify'
+ '-F' in 'ls'.
-`colons'
- `-c' in `recode'.
+'colons'
+ '-c' in 'recode'.
-`command'
- `-c' in `su'; `-x' in GDB.
+'command'
+ '-c' in 'su'; '-x' in GDB.
-`compare'
- `-d' in `tar'.
+'compare'
+ '-d' in 'tar'.
-`compat'
- Used in `gawk'.
+'compat'
+ Used in 'gawk'.
-`compress'
- `-Z' in `tar' and `shar'.
+'compress'
+ '-Z' in 'tar' and 'shar'.
-`concatenate'
- `-A' in `tar'.
+'concatenate'
+ '-A' in 'tar'.
-`confirmation'
- `-w' in `tar'.
+'confirmation'
+ '-w' in 'tar'.
-`context'
- Used in `diff'.
+'context'
+ Used in 'diff'.
-`copyleft'
- `-W copyleft' in `gawk'.
+'copyleft'
+ '-W copyleft' in 'gawk'.
-`copyright'
- `-C' in `ptx', `recode', and `wdiff'; `-W copyright' in `gawk'.
+'copyright'
+ '-C' in 'ptx', 'recode', and 'wdiff'; '-W copyright' in 'gawk'.
-`core'
+'core'
Used in GDB.
-`count'
- `-q' in `who'.
+'count'
+ '-q' in 'who'.
-`count-links'
- `-l' in `du'.
+'count-links'
+ '-l' in 'du'.
-`create'
- Used in `tar' and `cpio'.
+'create'
+ Used in 'tar' and 'cpio'.
-`cut-mark'
- `-c' in `shar'.
+'cut-mark'
+ '-c' in 'shar'.
-`cxref'
- `-x' in `ctags'.
+'cxref'
+ '-x' in 'ctags'.
-`date'
- `-d' in `touch'.
+'date'
+ '-d' in 'touch'.
-`debug'
- `-d' in `make' and `m4'; `-t' in Bison.
+'debug'
+ '-d' in 'make' and 'm4'; '-t' in Bison.
-`define'
- `-D' in `m4'.
+'define'
+ '-D' in 'm4'.
-`defines'
- `-d' in Bison and `ctags'.
+'defines'
+ '-d' in Bison and 'ctags'.
-`delete'
- `-D' in `tar'.
+'delete'
+ '-D' in 'tar'.
-`dereference'
- `-L' in `chgrp', `chown', `cpio', `du', `ls', and `tar'.
+'dereference'
+ '-L' in 'chgrp', 'chown', 'cpio', 'du', 'ls', and 'tar'.
-`dereference-args'
- `-D' in `du'.
+'dereference-args'
+ '-D' in 'du'.
-`device'
+'device'
Specify an I/O device (special file name).
-`diacritics'
- `-d' in `recode'.
+'diacritics'
+ '-d' in 'recode'.
-`dictionary-order'
- `-d' in `look'.
+'dictionary-order'
+ '-d' in 'look'.
-`diff'
- `-d' in `tar'.
+'diff'
+ '-d' in 'tar'.
-`digits'
- `-n' in `csplit'.
+'digits'
+ '-n' in 'csplit'.
-`directory'
- Specify the directory to use, in various programs. In `ls', it
+'directory'
+ Specify the directory to use, in various programs. In 'ls', it
means to show directories themselves rather than their contents.
- In `rm' and `ln', it means to not treat links to directories
+ In 'rm' and 'ln', it means to not treat links to directories
specially.
-`discard-all'
- `-x' in `strip'.
+'discard-all'
+ '-x' in 'strip'.
-`discard-locals'
- `-X' in `strip'.
+'discard-locals'
+ '-X' in 'strip'.
-`dry-run'
- `-n' in `make'.
+'dry-run'
+ '-n' in 'make'.
-`ed'
- `-e' in `diff'.
+'ed'
+ '-e' in 'diff'.
-`elide-empty-files'
- `-z' in `csplit'.
+'elide-empty-files'
+ '-z' in 'csplit'.
-`end-delete'
- `-x' in `wdiff'.
+'end-delete'
+ '-x' in 'wdiff'.
-`end-insert'
- `-z' in `wdiff'.
+'end-insert'
+ '-z' in 'wdiff'.
-`entire-new-file'
- `-N' in `diff'.
+'entire-new-file'
+ '-N' in 'diff'.
-`environment-overrides'
- `-e' in `make'.
+'environment-overrides'
+ '-e' in 'make'.
-`eof'
- `-e' in `xargs'.
+'eof'
+ '-e' in 'xargs'.
-`epoch'
+'epoch'
Used in GDB.
-`error-limit'
- Used in `makeinfo'.
+'error-limit'
+ Used in 'makeinfo'.
-`error-output'
- `-o' in `m4'.
+'error-output'
+ '-o' in 'm4'.
-`escape'
- `-b' in `ls'.
+'escape'
+ '-b' in 'ls'.
-`exclude-from'
- `-X' in `tar'.
+'exclude-from'
+ '-X' in 'tar'.
-`exec'
+'exec'
Used in GDB.
-`exit'
- `-x' in `xargs'.
+'exit'
+ '-x' in 'xargs'.
-`exit-0'
- `-e' in `unshar'.
+'exit-0'
+ '-e' in 'unshar'.
-`expand-tabs'
- `-t' in `diff'.
+'expand-tabs'
+ '-t' in 'diff'.
-`expression'
- `-e' in `sed'.
+'expression'
+ '-e' in 'sed'.
-`extern-only'
- `-g' in `nm'.
+'extern-only'
+ '-g' in 'nm'.
-`extract'
- `-i' in `cpio'; `-x' in `tar'.
+'extract'
+ '-i' in 'cpio'; '-x' in 'tar'.
-`faces'
- `-f' in `finger'.
+'faces'
+ '-f' in 'finger'.
-`fast'
- `-f' in `su'.
+'fast'
+ '-f' in 'su'.
-`fatal-warnings'
- `-E' in `m4'.
+'fatal-warnings'
+ '-E' in 'm4'.
-`file'
- `-f' in `gawk', `info', `make', `mt', `sed', and `tar'.
+'file'
+ '-f' in 'gawk', 'info', 'make', 'mt', 'sed', and 'tar'.
-`field-separator'
- `-F' in `gawk'.
+'field-separator'
+ '-F' in 'gawk'.
-`file-prefix'
- `-b' in Bison.
+'file-prefix'
+ '-b' in Bison.
-`file-type'
- `-F' in `ls'.
+'file-type'
+ '-F' in 'ls'.
-`files-from'
- `-T' in `tar'.
+'files-from'
+ '-T' in 'tar'.
-`fill-column'
- Used in `makeinfo'.
+'fill-column'
+ Used in 'makeinfo'.
-`flag-truncation'
- `-F' in `ptx'.
+'flag-truncation'
+ '-F' in 'ptx'.
-`fixed-output-files'
- `-y' in Bison.
+'fixed-output-files'
+ '-y' in Bison.
-`follow'
- `-f' in `tail'.
+'follow'
+ '-f' in 'tail'.
-`footnote-style'
- Used in `makeinfo'.
+'footnote-style'
+ Used in 'makeinfo'.
-`force'
- `-f' in `cp', `ln', `mv', and `rm'.
+'force'
+ '-f' in 'cp', 'ln', 'mv', and 'rm'.
-`force-prefix'
- `-F' in `shar'.
+'force-prefix'
+ '-F' in 'shar'.
-`foreground'
+'foreground'
For server programs, run in the foreground; in other words, don't
do anything special to run the server in the background.
-`format'
- Used in `ls', `time', and `ptx'.
+'format'
+ Used in 'ls', 'time', and 'ptx'.
-`freeze-state'
- `-F' in `m4'.
+'freeze-state'
+ '-F' in 'm4'.
-`fullname'
+'fullname'
Used in GDB.
-`gap-size'
- `-g' in `ptx'.
+'gap-size'
+ '-g' in 'ptx'.
-`get'
- `-x' in `tar'.
+'get'
+ '-x' in 'tar'.
-`graphic'
- `-i' in `ul'.
+'graphic'
+ '-i' in 'ul'.
-`graphics'
- `-g' in `recode'.
+'graphics'
+ '-g' in 'recode'.
-`group'
- `-g' in `install'.
+'group'
+ '-g' in 'install'.
-`gzip'
- `-z' in `tar' and `shar'.
+'gzip'
+ '-z' in 'tar' and 'shar'.
-`hashsize'
- `-H' in `m4'.
+'hashsize'
+ '-H' in 'm4'.
-`header'
- `-h' in `objdump' and `recode'
+'header'
+ '-h' in 'objdump' and 'recode'
-`heading'
- `-H' in `who'.
+'heading'
+ '-H' in 'who'.
-`help'
+'help'
Used to ask for brief usage information.
-`here-delimiter'
- `-d' in `shar'.
+'here-delimiter'
+ '-d' in 'shar'.
-`hide-control-chars'
- `-q' in `ls'.
+'hide-control-chars'
+ '-q' in 'ls'.
-`html'
- In `makeinfo', output HTML.
+'html'
+ In 'makeinfo', output HTML.
-`idle'
- `-u' in `who'.
+'idle'
+ '-u' in 'who'.
-`ifdef'
- `-D' in `diff'.
+'ifdef'
+ '-D' in 'diff'.
-`ignore'
- `-I' in `ls'; `-x' in `recode'.
+'ignore'
+ '-I' in 'ls'; '-x' in 'recode'.
-`ignore-all-space'
- `-w' in `diff'.
+'ignore-all-space'
+ '-w' in 'diff'.
-`ignore-backups'
- `-B' in `ls'.
+'ignore-backups'
+ '-B' in 'ls'.
-`ignore-blank-lines'
- `-B' in `diff'.
+'ignore-blank-lines'
+ '-B' in 'diff'.
-`ignore-case'
- `-f' in `look' and `ptx'; `-i' in `diff' and `wdiff'.
+'ignore-case'
+ '-f' in 'look' and 'ptx'; '-i' in 'diff' and 'wdiff'.
-`ignore-errors'
- `-i' in `make'.
+'ignore-errors'
+ '-i' in 'make'.
-`ignore-file'
- `-i' in `ptx'.
+'ignore-file'
+ '-i' in 'ptx'.
-`ignore-indentation'
- `-I' in `etags'.
+'ignore-indentation'
+ '-I' in 'etags'.
-`ignore-init-file'
- `-f' in Oleo.
+'ignore-init-file'
+ '-f' in Oleo.
-`ignore-interrupts'
- `-i' in `tee'.
+'ignore-interrupts'
+ '-i' in 'tee'.
-`ignore-matching-lines'
- `-I' in `diff'.
+'ignore-matching-lines'
+ '-I' in 'diff'.
-`ignore-space-change'
- `-b' in `diff'.
+'ignore-space-change'
+ '-b' in 'diff'.
-`ignore-zeros'
- `-i' in `tar'.
+'ignore-zeros'
+ '-i' in 'tar'.
-`include'
- `-i' in `etags'; `-I' in `m4'.
+'include'
+ '-i' in 'etags'; '-I' in 'm4'.
-`include-dir'
- `-I' in `make'.
+'include-dir'
+ '-I' in 'make'.
-`incremental'
- `-G' in `tar'.
+'incremental'
+ '-G' in 'tar'.
-`info'
- `-i', `-l', and `-m' in Finger.
+'info'
+ '-i', '-l', and '-m' in Finger.
-`init-file'
+'init-file'
In some programs, specify the name of the file to read as the
user's init file.
-`initial'
- `-i' in `expand'.
+'initial'
+ '-i' in 'expand'.
-`initial-tab'
- `-T' in `diff'.
+'initial-tab'
+ '-T' in 'diff'.
-`inode'
- `-i' in `ls'.
+'inode'
+ '-i' in 'ls'.
-`interactive'
- `-i' in `cp', `ln', `mv', `rm'; `-e' in `m4'; `-p' in `xargs'; `-w'
- in `tar'.
+'interactive'
+ '-i' in 'cp', 'ln', 'mv', 'rm'; '-e' in 'm4'; '-p' in 'xargs'; '-w'
+ in 'tar'.
-`intermix-type'
- `-p' in `shar'.
+'intermix-type'
+ '-p' in 'shar'.
-`iso-8601'
- Used in `date'
+'iso-8601'
+ Used in 'date'
-`jobs'
- `-j' in `make'.
+'jobs'
+ '-j' in 'make'.
-`just-print'
- `-n' in `make'.
+'just-print'
+ '-n' in 'make'.
-`keep-going'
- `-k' in `make'.
+'keep-going'
+ '-k' in 'make'.
-`keep-files'
- `-k' in `csplit'.
+'keep-files'
+ '-k' in 'csplit'.
-`kilobytes'
- `-k' in `du' and `ls'.
+'kilobytes'
+ '-k' in 'du' and 'ls'.
-`language'
- `-l' in `etags'.
+'language'
+ '-l' in 'etags'.
-`less-mode'
- `-l' in `wdiff'.
+'less-mode'
+ '-l' in 'wdiff'.
-`level-for-gzip'
- `-g' in `shar'.
+'level-for-gzip'
+ '-g' in 'shar'.
-`line-bytes'
- `-C' in `split'.
+'line-bytes'
+ '-C' in 'split'.
-`lines'
- Used in `split', `head', and `tail'.
+'lines'
+ Used in 'split', 'head', and 'tail'.
-`link'
- `-l' in `cpio'.
+'link'
+ '-l' in 'cpio'.
-`lint'
-`lint-old'
- Used in `gawk'.
+'lint'
+'lint-old'
+ Used in 'gawk'.
-`list'
- `-t' in `cpio'; `-l' in `recode'.
+'list'
+ '-t' in 'cpio'; '-l' in 'recode'.
-`list'
- `-t' in `tar'.
+'list'
+ '-t' in 'tar'.
-`literal'
- `-N' in `ls'.
+'literal'
+ '-N' in 'ls'.
-`load-average'
- `-l' in `make'.
+'load-average'
+ '-l' in 'make'.
-`login'
- Used in `su'.
+'login'
+ Used in 'su'.
-`machine'
- Used in `uname'.
+'machine'
+ Used in 'uname'.
-`macro-name'
- `-M' in `ptx'.
+'macro-name'
+ '-M' in 'ptx'.
-`mail'
- `-m' in `hello' and `uname'.
+'mail'
+ '-m' in 'hello' and 'uname'.
-`make-directories'
- `-d' in `cpio'.
+'make-directories'
+ '-d' in 'cpio'.
-`makefile'
- `-f' in `make'.
+'makefile'
+ '-f' in 'make'.
-`mapped'
+'mapped'
Used in GDB.
-`max-args'
- `-n' in `xargs'.
+'max-args'
+ '-n' in 'xargs'.
-`max-chars'
- `-n' in `xargs'.
+'max-chars'
+ '-n' in 'xargs'.
-`max-lines'
- `-l' in `xargs'.
+'max-lines'
+ '-l' in 'xargs'.
-`max-load'
- `-l' in `make'.
+'max-load'
+ '-l' in 'make'.
-`max-procs'
- `-P' in `xargs'.
+'max-procs'
+ '-P' in 'xargs'.
-`mesg'
- `-T' in `who'.
+'mesg'
+ '-T' in 'who'.
-`message'
- `-T' in `who'.
+'message'
+ '-T' in 'who'.
-`minimal'
- `-d' in `diff'.
+'minimal'
+ '-d' in 'diff'.
-`mixed-uuencode'
- `-M' in `shar'.
+'mixed-uuencode'
+ '-M' in 'shar'.
-`mode'
- `-m' in `install', `mkdir', and `mkfifo'.
+'mode'
+ '-m' in 'install', 'mkdir', and 'mkfifo'.
-`modification-time'
- `-m' in `tar'.
+'modification-time'
+ '-m' in 'tar'.
-`multi-volume'
- `-M' in `tar'.
+'multi-volume'
+ '-M' in 'tar'.
-`name-prefix'
- `-a' in Bison.
+'name-prefix'
+ '-a' in Bison.
-`nesting-limit'
- `-L' in `m4'.
+'nesting-limit'
+ '-L' in 'm4'.
-`net-headers'
- `-a' in `shar'.
+'net-headers'
+ '-a' in 'shar'.
-`new-file'
- `-W' in `make'.
+'new-file'
+ '-W' in 'make'.
-`no-builtin-rules'
- `-r' in `make'.
+'no-builtin-rules'
+ '-r' in 'make'.
-`no-character-count'
- `-w' in `shar'.
+'no-character-count'
+ '-w' in 'shar'.
-`no-check-existing'
- `-x' in `shar'.
+'no-check-existing'
+ '-x' in 'shar'.
-`no-common'
- `-3' in `wdiff'.
+'no-common'
+ '-3' in 'wdiff'.
-`no-create'
- `-c' in `touch'.
+'no-create'
+ '-c' in 'touch'.
-`no-defines'
- `-D' in `etags'.
+'no-defines'
+ '-D' in 'etags'.
-`no-deleted'
- `-1' in `wdiff'.
+'no-deleted'
+ '-1' in 'wdiff'.
-`no-dereference'
- `-d' in `cp'.
+'no-dereference'
+ '-d' in 'cp'.
-`no-inserted'
- `-2' in `wdiff'.
+'no-inserted'
+ '-2' in 'wdiff'.
-`no-keep-going'
- `-S' in `make'.
+'no-keep-going'
+ '-S' in 'make'.
-`no-lines'
- `-l' in Bison.
+'no-lines'
+ '-l' in Bison.
-`no-piping'
- `-P' in `shar'.
+'no-piping'
+ '-P' in 'shar'.
-`no-prof'
- `-e' in `gprof'.
+'no-prof'
+ '-e' in 'gprof'.
-`no-regex'
- `-R' in `etags'.
+'no-regex'
+ '-R' in 'etags'.
-`no-sort'
- `-p' in `nm'.
+'no-sort'
+ '-p' in 'nm'.
-`no-splash'
+'no-splash'
Don't print a startup splash screen.
-`no-split'
- Used in `makeinfo'.
+'no-split'
+ Used in 'makeinfo'.
-`no-static'
- `-a' in `gprof'.
+'no-static'
+ '-a' in 'gprof'.
-`no-time'
- `-E' in `gprof'.
+'no-time'
+ '-E' in 'gprof'.
-`no-timestamp'
- `-m' in `shar'.
+'no-timestamp'
+ '-m' in 'shar'.
-`no-validate'
- Used in `makeinfo'.
+'no-validate'
+ Used in 'makeinfo'.
-`no-wait'
- Used in `emacsclient'.
+'no-wait'
+ Used in 'emacsclient'.
-`no-warn'
+'no-warn'
Used in various programs to inhibit warnings.
-`node'
- `-n' in `info'.
+'node'
+ '-n' in 'info'.
-`nodename'
- `-n' in `uname'.
+'nodename'
+ '-n' in 'uname'.
-`nonmatching'
- `-f' in `cpio'.
+'nonmatching'
+ '-f' in 'cpio'.
-`nstuff'
- `-n' in `objdump'.
+'nstuff'
+ '-n' in 'objdump'.
-`null'
- `-0' in `xargs'.
+'null'
+ '-0' in 'xargs'.
-`number'
- `-n' in `cat'.
+'number'
+ '-n' in 'cat'.
-`number-nonblank'
- `-b' in `cat'.
+'number-nonblank'
+ '-b' in 'cat'.
-`numeric-sort'
- `-n' in `nm'.
+'numeric-sort'
+ '-n' in 'nm'.
-`numeric-uid-gid'
- `-n' in `cpio' and `ls'.
+'numeric-uid-gid'
+ '-n' in 'cpio' and 'ls'.
-`nx'
+'nx'
Used in GDB.
-`old-archive'
- `-o' in `tar'.
+'old-archive'
+ '-o' in 'tar'.
-`old-file'
- `-o' in `make'.
+'old-file'
+ '-o' in 'make'.
-`one-file-system'
- `-l' in `tar', `cp', and `du'.
+'one-file-system'
+ '-l' in 'tar', 'cp', and 'du'.
-`only-file'
- `-o' in `ptx'.
+'only-file'
+ '-o' in 'ptx'.
-`only-prof'
- `-f' in `gprof'.
+'only-prof'
+ '-f' in 'gprof'.
-`only-time'
- `-F' in `gprof'.
+'only-time'
+ '-F' in 'gprof'.
-`options'
- `-o' in `getopt', `fdlist', `fdmount', `fdmountd', and `fdumount'.
+'options'
+ '-o' in 'getopt', 'fdlist', 'fdmount', 'fdmountd', and 'fdumount'.
-`output'
+'output'
In various programs, specify the output file name.
-`output-prefix'
- `-o' in `shar'.
+'output-prefix'
+ '-o' in 'shar'.
-`override'
- `-o' in `rm'.
+'override'
+ '-o' in 'rm'.
-`overwrite'
- `-c' in `unshar'.
+'overwrite'
+ '-c' in 'unshar'.
-`owner'
- `-o' in `install'.
+'owner'
+ '-o' in 'install'.
-`paginate'
- `-l' in `diff'.
+'paginate'
+ '-l' in 'diff'.
-`paragraph-indent'
- Used in `makeinfo'.
+'paragraph-indent'
+ Used in 'makeinfo'.
-`parents'
- `-p' in `mkdir' and `rmdir'.
+'parents'
+ '-p' in 'mkdir' and 'rmdir'.
-`pass-all'
- `-p' in `ul'.
+'pass-all'
+ '-p' in 'ul'.
-`pass-through'
- `-p' in `cpio'.
+'pass-through'
+ '-p' in 'cpio'.
-`port'
- `-P' in `finger'.
+'port'
+ '-P' in 'finger'.
-`portability'
- `-c' in `cpio' and `tar'.
+'portability'
+ '-c' in 'cpio' and 'tar'.
-`posix'
- Used in `gawk'.
+'posix'
+ Used in 'gawk'.
-`prefix-builtins'
- `-P' in `m4'.
+'prefix-builtins'
+ '-P' in 'm4'.
-`prefix'
- `-f' in `csplit'.
+'prefix'
+ '-f' in 'csplit'.
-`preserve'
- Used in `tar' and `cp'.
+'preserve'
+ Used in 'tar' and 'cp'.
-`preserve-environment'
- `-p' in `su'.
+'preserve-environment'
+ '-p' in 'su'.
-`preserve-modification-time'
- `-m' in `cpio'.
+'preserve-modification-time'
+ '-m' in 'cpio'.
-`preserve-order'
- `-s' in `tar'.
+'preserve-order'
+ '-s' in 'tar'.
-`preserve-permissions'
- `-p' in `tar'.
+'preserve-permissions'
+ '-p' in 'tar'.
-`print'
- `-l' in `diff'.
+'print'
+ '-l' in 'diff'.
-`print-chars'
- `-L' in `cmp'.
+'print-chars'
+ '-L' in 'cmp'.
-`print-data-base'
- `-p' in `make'.
+'print-data-base'
+ '-p' in 'make'.
-`print-directory'
- `-w' in `make'.
+'print-directory'
+ '-w' in 'make'.
-`print-file-name'
- `-o' in `nm'.
+'print-file-name'
+ '-o' in 'nm'.
-`print-symdefs'
- `-s' in `nm'.
+'print-symdefs'
+ '-s' in 'nm'.
-`printer'
- `-p' in `wdiff'.
+'printer'
+ '-p' in 'wdiff'.
-`prompt'
- `-p' in `ed'.
+'prompt'
+ '-p' in 'ed'.
-`proxy'
+'proxy'
Specify an HTTP proxy.
-`query-user'
- `-X' in `shar'.
+'query-user'
+ '-X' in 'shar'.
-`question'
- `-q' in `make'.
+'question'
+ '-q' in 'make'.
-`quiet'
+'quiet'
Used in many programs to inhibit the usual output. Every program
- accepting `--quiet' should accept `--silent' as a synonym.
+ accepting '--quiet' should accept '--silent' as a synonym.
-`quiet-unshar'
- `-Q' in `shar'
+'quiet-unshar'
+ '-Q' in 'shar'
-`quote-name'
- `-Q' in `ls'.
+'quote-name'
+ '-Q' in 'ls'.
-`rcs'
- `-n' in `diff'.
+'rcs'
+ '-n' in 'diff'.
-`re-interval'
- Used in `gawk'.
+'re-interval'
+ Used in 'gawk'.
-`read-full-blocks'
- `-B' in `tar'.
+'read-full-blocks'
+ '-B' in 'tar'.
-`readnow'
+'readnow'
Used in GDB.
-`recon'
- `-n' in `make'.
+'recon'
+ '-n' in 'make'.
-`record-number'
- `-R' in `tar'.
+'record-number'
+ '-R' in 'tar'.
-`recursive'
- Used in `chgrp', `chown', `cp', `ls', `diff', and `rm'.
+'recursive'
+ Used in 'chgrp', 'chown', 'cp', 'ls', 'diff', and 'rm'.
-`reference'
- `-r' in `touch'.
+'reference'
+ '-r' in 'touch'.
-`references'
- `-r' in `ptx'.
+'references'
+ '-r' in 'ptx'.
-`regex'
- `-r' in `tac' and `etags'.
+'regex'
+ '-r' in 'tac' and 'etags'.
-`release'
- `-r' in `uname'.
+'release'
+ '-r' in 'uname'.
-`reload-state'
- `-R' in `m4'.
+'reload-state'
+ '-R' in 'm4'.
-`relocation'
- `-r' in `objdump'.
+'relocation'
+ '-r' in 'objdump'.
-`rename'
- `-r' in `cpio'.
+'rename'
+ '-r' in 'cpio'.
-`replace'
- `-i' in `xargs'.
+'replace'
+ '-i' in 'xargs'.
-`report-identical-files'
- `-s' in `diff'.
+'report-identical-files'
+ '-s' in 'diff'.
-`reset-access-time'
- `-a' in `cpio'.
+'reset-access-time'
+ '-a' in 'cpio'.
-`reverse'
- `-r' in `ls' and `nm'.
+'reverse'
+ '-r' in 'ls' and 'nm'.
-`reversed-ed'
- `-f' in `diff'.
+'reversed-ed'
+ '-f' in 'diff'.
-`right-side-defs'
- `-R' in `ptx'.
+'right-side-defs'
+ '-R' in 'ptx'.
-`same-order'
- `-s' in `tar'.
+'same-order'
+ '-s' in 'tar'.
-`same-permissions'
- `-p' in `tar'.
+'same-permissions'
+ '-p' in 'tar'.
-`save'
- `-g' in `stty'.
+'save'
+ '-g' in 'stty'.
-`se'
+'se'
Used in GDB.
-`sentence-regexp'
- `-S' in `ptx'.
+'sentence-regexp'
+ '-S' in 'ptx'.
-`separate-dirs'
- `-S' in `du'.
+'separate-dirs'
+ '-S' in 'du'.
-`separator'
- `-s' in `tac'.
+'separator'
+ '-s' in 'tac'.
-`sequence'
- Used by `recode' to chose files or pipes for sequencing passes.
+'sequence'
+ Used by 'recode' to chose files or pipes for sequencing passes.
-`shell'
- `-s' in `su'.
+'shell'
+ '-s' in 'su'.
-`show-all'
- `-A' in `cat'.
+'show-all'
+ '-A' in 'cat'.
-`show-c-function'
- `-p' in `diff'.
+'show-c-function'
+ '-p' in 'diff'.
-`show-ends'
- `-E' in `cat'.
+'show-ends'
+ '-E' in 'cat'.
-`show-function-line'
- `-F' in `diff'.
+'show-function-line'
+ '-F' in 'diff'.
-`show-tabs'
- `-T' in `cat'.
+'show-tabs'
+ '-T' in 'cat'.
-`silent'
+'silent'
Used in many programs to inhibit the usual output. Every program
- accepting `--silent' should accept `--quiet' as a synonym.
+ accepting '--silent' should accept '--quiet' as a synonym.
-`size'
- `-s' in `ls'.
+'size'
+ '-s' in 'ls'.
-`socket'
+'socket'
Specify a file descriptor for a network server to use for its
socket, instead of opening and binding a new socket. This provides
a way to run, in a non-privileged process, a server that normally
needs a reserved port number.
-`sort'
- Used in `ls'.
+'sort'
+ Used in 'ls'.
-`source'
- `-W source' in `gawk'.
+'source'
+ '-W source' in 'gawk'.
-`sparse'
- `-S' in `tar'.
+'sparse'
+ '-S' in 'tar'.
-`speed-large-files'
- `-H' in `diff'.
+'speed-large-files'
+ '-H' in 'diff'.
-`split-at'
- `-E' in `unshar'.
+'split-at'
+ '-E' in 'unshar'.
-`split-size-limit'
- `-L' in `shar'.
+'split-size-limit'
+ '-L' in 'shar'.
-`squeeze-blank'
- `-s' in `cat'.
+'squeeze-blank'
+ '-s' in 'cat'.
-`start-delete'
- `-w' in `wdiff'.
+'start-delete'
+ '-w' in 'wdiff'.
-`start-insert'
- `-y' in `wdiff'.
+'start-insert'
+ '-y' in 'wdiff'.
-`starting-file'
- Used in `tar' and `diff' to specify which file within a directory
+'starting-file'
+ Used in 'tar' and 'diff' to specify which file within a directory
to start processing with.
-`statistics'
- `-s' in `wdiff'.
+'statistics'
+ '-s' in 'wdiff'.
-`stdin-file-list'
- `-S' in `shar'.
+'stdin-file-list'
+ '-S' in 'shar'.
-`stop'
- `-S' in `make'.
+'stop'
+ '-S' in 'make'.
-`strict'
- `-s' in `recode'.
+'strict'
+ '-s' in 'recode'.
-`strip'
- `-s' in `install'.
+'strip'
+ '-s' in 'install'.
-`strip-all'
- `-s' in `strip'.
+'strip-all'
+ '-s' in 'strip'.
-`strip-debug'
- `-S' in `strip'.
+'strip-debug'
+ '-S' in 'strip'.
-`submitter'
- `-s' in `shar'.
+'submitter'
+ '-s' in 'shar'.
-`suffix'
- `-S' in `cp', `ln', `mv'.
+'suffix'
+ '-S' in 'cp', 'ln', 'mv'.
-`suffix-format'
- `-b' in `csplit'.
+'suffix-format'
+ '-b' in 'csplit'.
-`sum'
- `-s' in `gprof'.
+'sum'
+ '-s' in 'gprof'.
-`summarize'
- `-s' in `du'.
+'summarize'
+ '-s' in 'du'.
-`symbolic'
- `-s' in `ln'.
+'symbolic'
+ '-s' in 'ln'.
-`symbols'
- Used in GDB and `objdump'.
+'symbols'
+ Used in GDB and 'objdump'.
-`synclines'
- `-s' in `m4'.
+'synclines'
+ '-s' in 'm4'.
-`sysname'
- `-s' in `uname'.
+'sysname'
+ '-s' in 'uname'.
-`tabs'
- `-t' in `expand' and `unexpand'.
+'tabs'
+ '-t' in 'expand' and 'unexpand'.
-`tabsize'
- `-T' in `ls'.
+'tabsize'
+ '-T' in 'ls'.
-`terminal'
- `-T' in `tput' and `ul'. `-t' in `wdiff'.
+'terminal'
+ '-T' in 'tput' and 'ul'. '-t' in 'wdiff'.
-`text'
- `-a' in `diff'.
+'text'
+ '-a' in 'diff'.
-`text-files'
- `-T' in `shar'.
+'text-files'
+ '-T' in 'shar'.
-`time'
- Used in `ls' and `touch'.
+'time'
+ Used in 'ls' and 'touch'.
-`timeout'
+'timeout'
Specify how long to wait before giving up on some operation.
-`to-stdout'
- `-O' in `tar'.
+'to-stdout'
+ '-O' in 'tar'.
-`total'
- `-c' in `du'.
+'total'
+ '-c' in 'du'.
-`touch'
- `-t' in `make', `ranlib', and `recode'.
+'touch'
+ '-t' in 'make', 'ranlib', and 'recode'.
-`trace'
- `-t' in `m4'.
+'trace'
+ '-t' in 'm4'.
-`traditional'
- `-t' in `hello'; `-W traditional' in `gawk'; `-G' in `ed', `m4',
- and `ptx'.
+'traditional'
+ '-t' in 'hello'; '-W traditional' in 'gawk'; '-G' in 'ed', 'm4',
+ and 'ptx'.
-`tty'
+'tty'
Used in GDB.
-`typedefs'
- `-t' in `ctags'.
+'typedefs'
+ '-t' in 'ctags'.
-`typedefs-and-c++'
- `-T' in `ctags'.
+'typedefs-and-c++'
+ '-T' in 'ctags'.
-`typeset-mode'
- `-t' in `ptx'.
+'typeset-mode'
+ '-t' in 'ptx'.
-`uncompress'
- `-z' in `tar'.
+'uncompress'
+ '-z' in 'tar'.
-`unconditional'
- `-u' in `cpio'.
+'unconditional'
+ '-u' in 'cpio'.
-`undefine'
- `-U' in `m4'.
+'undefine'
+ '-U' in 'm4'.
-`undefined-only'
- `-u' in `nm'.
+'undefined-only'
+ '-u' in 'nm'.
-`update'
- `-u' in `cp', `ctags', `mv', `tar'.
+'update'
+ '-u' in 'cp', 'ctags', 'mv', 'tar'.
-`usage'
- Used in `gawk'; same as `--help'.
+'usage'
+ Used in 'gawk'; same as '--help'.
-`uuencode'
- `-B' in `shar'.
+'uuencode'
+ '-B' in 'shar'.
-`vanilla-operation'
- `-V' in `shar'.
+'vanilla-operation'
+ '-V' in 'shar'.
-`verbose'
+'verbose'
Print more information about progress. Many programs support this.
-`verify'
- `-W' in `tar'.
+'verify'
+ '-W' in 'tar'.
-`version'
+'version'
Print the version number.
-`version-control'
- `-V' in `cp', `ln', `mv'.
+'version-control'
+ '-V' in 'cp', 'ln', 'mv'.
-`vgrind'
- `-v' in `ctags'.
+'vgrind'
+ '-v' in 'ctags'.
-`volume'
- `-V' in `tar'.
+'volume'
+ '-V' in 'tar'.
-`what-if'
- `-W' in `make'.
+'what-if'
+ '-W' in 'make'.
-`whole-size-limit'
- `-l' in `shar'.
+'whole-size-limit'
+ '-l' in 'shar'.
-`width'
- `-w' in `ls' and `ptx'.
+'width'
+ '-w' in 'ls' and 'ptx'.
-`word-regexp'
- `-W' in `ptx'.
+'word-regexp'
+ '-W' in 'ptx'.
-`writable'
- `-T' in `who'.
+'writable'
+ '-T' in 'who'.
-`zeros'
- `-z' in `gprof'.
+'zeros'
+ '-z' in 'gprof'.
4.10 OID Allocations
====================
@@ -2084,7 +2084,7 @@
The OID (object identifier) 1.3.6.1.4.1.11591 has been assigned to the
GNU Project (thanks to Werner Koch). These are used for SNMP, LDAP,
X.509 certificates, and so on. The web site
-`http://www.alvestrand.no/objectid' has a (voluntary) listing of many
+'http://www.alvestrand.no/objectid' has a (voluntary) listing of many
OID assignments.
If you need a new slot for your GNU package, write
@@ -2139,7 +2139,7 @@
long, it is reasonable to read entire input files into memory to operate
on them.
- However, for programs such as `cat' or `tail', that can usefully
+ However, for programs such as 'cat' or 'tail', that can usefully
operate on very large files, it is important to avoid using a technique
that would artificially limit the size of files it can handle. If a
program works by lines and could be applied to arbitrary user-supplied
@@ -2148,9 +2148,9 @@
are bigger than will fit in memory all at once.
If your program creates complicated data structures, just make them
-in memory and give a fatal error if `malloc' returns zero.
+in memory and give a fatal error if 'malloc' returns zero.
- Memory analysis tools such as `valgrind' can be useful, but don't
+ Memory analysis tools such as 'valgrind' can be useful, but don't
complicate a program merely to avoid their false alarms. For example,
if memory is used until just before a process exits, don't free it
simply to silence such a tool.
@@ -2158,15 +2158,15 @@
4.12 File Usage
===============
-Programs should be prepared to operate when `/usr' and `/etc' are
+Programs should be prepared to operate when '/usr' and '/etc' are
read-only file systems. Thus, if the program manages log files, lock
files, backup files, score files, or any other files which are modified
-for internal purposes, these files should not be stored in `/usr' or
-`/etc'.
+for internal purposes, these files should not be stored in '/usr' or
+'/etc'.
- There are two exceptions. `/etc' is used to store system
+ There are two exceptions. '/etc' is used to store system
configuration information; it is reasonable for a program to modify
-files in `/etc' when its job is to update the system configuration.
+files in '/etc' when its job is to update the system configuration.
Also, if the user explicitly asks to modify one file in a directory, it
is reasonable for the program to store other files in the same
directory.
@@ -2187,7 +2187,7 @@
Avoid putting open-brace, open-parenthesis or open-bracket in column
one when they are inside a function, so that they won't start a defun.
-The open-brace that starts a `struct' body can go in column one if you
+The open-brace that starts a 'struct' body can go in column one if you
find it useful to treat that definition as a defun.
It is also important for function definitions to start the name of
@@ -2220,7 +2220,7 @@
...
The rest of this section gives our recommendations for other aspects
-of C formatting style, which is also the default style of the `indent'
+of C formatting style, which is also the default style of the 'indent'
program in version 1.2 and newer. It corresponds to the options
-nbad -bap -nbc -bbo -bl -bli2 -bls -ncdb -nce -cp1 -cs -di2
@@ -2301,8 +2301,8 @@
========================
Every program should start with a comment saying briefly what it is for.
-Example: `fmt - filter for simple filling of text'. This comment should
-be at the top of the source file containing the `main' function of the
+Example: 'fmt - filter for simple filling of text'. This comment should
+be at the top of the source file containing the 'main' function of the
program.
Also, please write a brief comment at the start of each source file,
@@ -2321,7 +2321,7 @@
arguments mean and are used for. It is not necessary to duplicate in
words the meaning of the C argument declarations, if a C type is being
used in its customary fashion. If there is anything nonstandard about
-its use (such as an argument of type `char *' which is really the
+its use (such as an argument of type 'char *' which is really the
address of the second character of a string, not the first), or any
possible values that would not work the way one would expect (such as,
that strings containing newlines are not guaranteed to work), be sure to
@@ -2354,10 +2354,10 @@
zero means continue them. */
int truncate_lines;
- Every `#endif' should have a comment, except in the case of short
+ Every '#endif' should have a comment, except in the case of short
conditionals (just a few lines) that are not nested. The comment should
state the condition of the conditional that is ending, _including its
-sense_. `#else' should have a comment describing the condition _and
+sense_. '#else' should have a comment describing the condition _and
sense_ of the code that follows. For example:
#ifdef foo
@@ -2369,7 +2369,7 @@
...
#endif /* foo */
-but, by contrast, write the comments this way for a `#ifndef':
+but, by contrast, write the comments this way for a '#ifndef':
#ifndef foo
...
@@ -2385,31 +2385,31 @@
Please explicitly declare the types of all objects. For example, you
should explicitly declare all arguments to functions, and you should
-declare functions to return `int' rather than omitting the `int'.
+declare functions to return 'int' rather than omitting the 'int'.
- Some programmers like to use the GCC `-Wall' option, and change the
+ Some programmers like to use the GCC '-Wall' option, and change the
code whenever it issues a warning. If you want to do this, then do.
-Other programmers prefer not to use `-Wall', because it gives warnings
+Other programmers prefer not to use '-Wall', because it gives warnings
for valid and legitimate code which they do not want to change. If you
want to do this, then do. The compiler should be your servant, not your
master.
Don't make the program ugly just to placate static analysis tools
-such as `lint', `clang', and GCC with extra warnings options such as
-`-Wconversion' and `-Wundef'. These tools can help find bugs and
-unclear code, but they can also generate so many false alarms that that
-it hurts readability to silence them with unnecessary casts, wrappers,
-and other complications. For example, please don't insert casts to
-`void' or calls to do-nothing functions merely to pacify a lint checker.
+such as 'lint', 'clang', and GCC with extra warnings options such as
+'-Wconversion' and '-Wundef'. These tools can help find bugs and
+unclear code, but they can also generate so many false alarms that it
+hurts readability to silence them with unnecessary casts, wrappers, and
+other complications. For example, please don't insert casts to 'void'
+or calls to do-nothing functions merely to pacify a lint checker.
Declarations of external functions and functions to appear later in
the source file should all go in one place near the beginning of the
file (somewhere before the first function definition in the file), or
-else should go in a header file. Don't put `extern' declarations inside
+else should go in a header file. Don't put 'extern' declarations inside
functions.
It used to be common practice to use the same local variables (with
-names like `tem') over and over for different values within one
+names like 'tem') over and over for different values within one
function. Instead of doing this, it is better to declare a separate
local variable for each distinct purpose, and give it a name which is
meaningful. This not only makes programs easier to understand, it also
@@ -2418,7 +2418,7 @@
all its uses. This makes the program even cleaner.
Don't use local variables or parameters that shadow global
-identifiers. GCC's `-Wshadow' option can detect this problem.
+identifiers. GCC's '-Wshadow' option can detect this problem.
Don't declare multiple variables in one declaration that spans lines.
Start a new declaration on each line, instead. For example, instead of
@@ -2439,8 +2439,8 @@
(If they are global variables, each should have a comment preceding it
anyway.)
- When you have an `if'-`else' statement nested in another `if'
-statement, always put braces around the `if'-`else'. Thus, never write
+ When you have an 'if'-'else' statement nested in another 'if'
+statement, always put braces around the 'if'-'else'. Thus, never write
like this:
if (foo)
@@ -2459,16 +2459,16 @@
lose ();
}
- If you have an `if' statement nested inside of an `else' statement,
-either write `else if' on one line, like this,
+ If you have an 'if' statement nested inside of an 'else' statement,
+either write 'else if' on one line, like this,
if (foo)
...
else if (bar)
...
-with its `then'-part indented like the preceding `then'-part, or write
-the nested `if' within braces like this:
+with its 'then'-part indented like the preceding 'then'-part, or write
+the nested 'if' within braces like this:
if (foo)
...
@@ -2482,8 +2482,8 @@
same declaration. Instead, declare the structure tag separately and
then use it to declare the variables or typedefs.
- Try to avoid assignments inside `if'-conditions (assignments inside
-`while'-conditions are ok). For example, don't write this:
+ Try to avoid assignments inside 'if'-conditions (assignments inside
+'while'-conditions are ok). For example, don't write this:
if ((foo = (char *) malloc (sizeof *foo)) == 0)
fatal ("virtual memory exhausted");
@@ -2496,7 +2496,7 @@
This example uses zero without a cast as a null pointer constant.
This is perfectly fine, except that a cast is needed when calling a
-varargs function or when using `sizeof'.
+varargs function or when using 'sizeof'.
5.4 Naming Variables, Functions, and Files
==========================================
@@ -2516,11 +2516,11 @@
Please use underscores to separate words in a name, so that the Emacs
word commands can be useful within them. Stick to lower case; reserve
-upper case for macros and `enum' constants, and for name-prefixes that
+upper case for macros and 'enum' constants, and for name-prefixes that
follow a uniform convention.
- For example, you should use names like `ignore_space_change_flag';
-don't use names like `iCantReadThis'.
+ For example, you should use names like 'ignore_space_change_flag';
+don't use names like 'iCantReadThis'.
Variables that indicate whether command-line options have been
specified should be named after the meaning of the option, not after the
@@ -2531,17 +2531,17 @@
int ignore_space_change_flag;
When you want to define names with constant integer values, use
-`enum' rather than `#define'. GDB knows about enumeration constants.
+'enum' rather than '#define'. GDB knows about enumeration constants.
You might want to make sure that none of the file names would
conflict if the files were loaded onto an MS-DOS file system which
-shortens the names. You can use the program `doschk' to test for this.
+shortens the names. You can use the program 'doschk' to test for this.
Some GNU programs were designed to limit themselves to file names of
14 characters or less, to avoid file name conflicts if they are read
into older System V systems. Please preserve this feature in the
existing GNU programs that have it, but there is no need to do this in
-new GNU programs. `doschk' also reports file names longer than 14
+new GNU programs. 'doschk' also reports file names longer than 14
characters.
5.5 Portability between System Types
@@ -2571,7 +2571,7 @@
written.
Avoid using the format of semi-internal data bases (e.g.,
-directories) when there is a higher-level alternative (`readdir').
+directories) when there is a higher-level alternative ('readdir').
As for systems that are not like Unix, such as MSDOS, Windows, VMS,
MVS, and older Macintosh systems, supporting them is often a lot of
@@ -2584,10 +2584,10 @@
You're free to praise Microsoft Windows on your own if you want, but
please don't do this in GNU packages. Instead of abbreviating "Windows"
to "win", you can write it in full or abbreviate it to "woe" or "w". In
-GNU Emacs, for instance, we use `w32' in file names of Windows-specific
-files, but the macro for Windows conditionals is called `WINDOWSNT'.
+GNU Emacs, for instance, we use 'w32' in file names of Windows-specific
+files, but the macro for Windows conditionals is called 'WINDOWSNT'.
- It is a good idea to define the "feature test macro" `_GNU_SOURCE'
+ It is a good idea to define the "feature test macro" '_GNU_SOURCE'
when compiling your C files. When you compile on GNU or GNU/Linux, this
will enable the declarations of GNU library extension functions, and
that will usually give you a compiler error message if you define the
@@ -2605,11 +2605,11 @@
Even GNU systems will differ because of differences among CPU types--for
example, difference in byte ordering and alignment requirements. It is
absolutely essential to handle these differences. However, don't make
-any effort to cater to the possibility that an `int' will be less than
+any effort to cater to the possibility that an 'int' will be less than
32 bits. We don't support 16-bit machines in GNU.
Similarly, don't make any effort to cater to the possibility that
-`long' will be smaller than predefined types like `size_t'. For
+'long' will be smaller than predefined types like 'size_t'. For
example, the following code is ok:
printf ("size = %lu\n", (unsigned long) sizeof array);
@@ -2620,12 +2620,12 @@
to those who want to port GNU programs to that environment to figure out
how to do it.
- Predefined file-size types like `off_t' are an exception: they are
-longer than `long' on many platforms, so code like the above won't work
-with them. One way to print an `off_t' value portably is to print its
+ Predefined file-size types like 'off_t' are an exception: they are
+longer than 'long' on many platforms, so code like the above won't work
+with them. One way to print an 'off_t' value portably is to print its
digits yourself, one by one.
- Don't assume that the address of an `int' object is also the address
+ Don't assume that the address of an 'int' object is also the address
of its least-significant byte. This is false on big-endian machines.
Thus, don't make the following mistake:
@@ -2634,8 +2634,8 @@
while ((c = getchar ()) != EOF)
write (file_descriptor, &c, 1);
-Instead, use `unsigned char' as follows. (The `unsigned' is for
-portability to unusual systems where `char' is signed and where there is
+Instead, use 'unsigned char' as follows. (The 'unsigned' is for
+portability to unusual systems where 'char' is signed and where there is
integer overflow checking.)
int c;
@@ -2651,7 +2651,7 @@
interpreter which stores type information as well as an address in one
word--you'll have to make explicit provisions to handle different word
sizes. You will also need to make provision for systems in which the
-normal range of addresses you can get from `malloc' starts far away from
+normal range of addresses you can get from 'malloc' starts far away from
zero.
5.7 Calling System Functions
@@ -2674,19 +2674,19 @@
Despite the standards, nearly every library function has some sort of
portability issue on some system or another. Here are some examples:
-`open'
- Names with trailing `/''s are mishandled on many platforms.
+'open'
+ Names with trailing '/''s are mishandled on many platforms.
-`printf'
- `long double' may be unimplemented; floating values Infinity and
+'printf'
+ 'long double' may be unimplemented; floating values Infinity and
NaN are often mishandled; output for large precisions may be
incorrect.
-`readlink'
- May return `int' instead of `ssize_t'.
+'readlink'
+ May return 'int' instead of 'ssize_t'.
-`scanf'
- On Windows, `errno' is not set on failure.
+'scanf'
+ On Windows, 'errno' is not set on failure.
Gnulib (http://www.gnu.org/software/gnulib/) is a big help in this
regard. Gnulib provides implementations of standard interfaces on many
@@ -2698,7 +2698,7 @@
Gnulib also provides many useful non-standard interfaces; for
example, C implementations of standard data structures (hash tables,
binary trees), error-checking type-safe wrappers for memory allocation
-functions (`xmalloc', `xrealloc'), and output of error messages.
+functions ('xmalloc', 'xrealloc'), and output of error messages.
Gnulib integrates with GNU Autoconf and Automake to remove much of
the burden of writing portable code from the programmer: Gnulib makes
@@ -2719,22 +2719,22 @@
in the program, and let gettext provide the way to translate them into
other languages.
- Using GNU gettext involves putting a call to the `gettext' macro
+ Using GNU gettext involves putting a call to the 'gettext' macro
around each string that might need translation--like this:
printf (gettext ("Processing file '%s'..."), file);
-This permits GNU gettext to replace the string `"Processing file
+This permits GNU gettext to replace the string '"Processing file
'%s'..."' with a translated version.
Once a program uses gettext, please make a point of writing calls to
-`gettext' when you add new strings that call for translation.
+'gettext' when you add new strings that call for translation.
Using GNU gettext in a package involves specifying a "text domain
name" for the package. The text domain name is used to separate the
translations for this package from the translations for other packages.
Normally, the text domain name should be the same as the name of the
-package--for example, `coreutils' for the GNU core utilities.
+package--for example, 'coreutils' for the GNU core utilities.
To enable gettext to work well, avoid writing code that makes
assumptions about the structure of words or sentences. When you want
@@ -2769,9 +2769,9 @@
printf ("# Implicit rule search has%s been done.\n",
f->tried_implicit ? "" : " not");
-Adding `gettext' calls to this code cannot give correct results for all
+Adding 'gettext' calls to this code cannot give correct results for all
languages, because negation in some languages requires adding words at
-more than one place in the sentence. By contrast, adding `gettext'
+more than one place in the sentence. By contrast, adding 'gettext'
calls does the job straightforwardly if the code starts out like this:
printf (f->tried_implicit
@@ -2784,13 +2784,13 @@
nfiles != 1 ? "s" : "");
The problem with this example is that it assumes that plurals are made
-by adding `s'. If you apply gettext to the format string, like this,
+by adding 's'. If you apply gettext to the format string, like this,
printf (gettext ("%d file%s processed"), nfiles,
nfiles != 1 ? "s" : "");
the message can use different words, but it will still be forced to use
-`s' for the plural. Here is a better way, with gettext being applied to
+'s' for the plural. Here is a better way, with gettext being applied to
the two strings independently:
printf ((nfiles != 1 ? gettext ("%d files processed")
@@ -2799,7 +2799,7 @@
But this still doesn't work for languages like Polish, which has three
plural forms: one for nfiles == 1, one for nfiles == 2, 3, 4, 22, 23,
-24, ... and one for the rest. The GNU `ngettext' function solves this
+24, ... and one for the rest. The GNU 'ngettext' function solves this
problem:
printf (ngettext ("%d files processed", "%d file processed", nfiles),
@@ -2825,11 +2825,11 @@
=====================
In the C locale, the output of GNU programs should stick to plain ASCII
-for quotation characters in messages to users: preferably 0x22 (`"') or
-0x27 (`'') for both opening and closing quotes. Although GNU programs
-traditionally used 0x60 (``') for opening and 0x27 (`'') for closing
-quotes, nowadays quotes ``like this'' are typically rendered
-asymmetrically, so quoting `"like this"' or `'like this'' typically
+for quotation characters in messages to users: preferably 0x22 ('"') or
+0x27 (''') for both opening and closing quotes. Although GNU programs
+traditionally used 0x60 ('`') for opening and 0x27 (''') for closing
+quotes, nowadays quotes '`like this'' are typically rendered
+asymmetrically, so quoting '"like this"' or ''like this'' typically
looks better.
It is ok, but not required, for GNU programs to generate
@@ -2837,13 +2837,13 @@
printf (gettext ("Processing file '%s'..."), file);
-Here, a French translation might cause `gettext' to return the string
-`"Traitement de fichier < %s >..."', yielding quotes more appropriate
+Here, a French translation might cause 'gettext' to return the string
+'"Traitement de fichier < %s >..."', yielding quotes more appropriate
for a French locale.
Sometimes a program may need to use opening and closing quotes
-directly. By convention, `gettext' translates the string `"`"' to the
-opening quote and the string `"'"' to the closing quote, and a program
+directly. By convention, 'gettext' translates the string '"`"' to the
+opening quote and the string '"'"' to the closing quote, and a program
can use these translations. Generally, though, it is better to
translate quote characters in the context of longer strings.
@@ -2851,21 +2851,21 @@
program, it is good to provide an option that makes this parsing
reliable. For example, you could escape special characters using
conventions from the C language or the Bourne shell. See for example
-the option `--quoting-style' of GNU `ls'.
+the option '--quoting-style' of GNU 'ls'.
5.11 Mmap
=========
-Don't assume that `mmap' either works on all files or fails for all
+Don't assume that 'mmap' either works on all files or fails for all
files. It may work on some files and fail on others.
- The proper way to use `mmap' is to try it on the specific file for
-which you want to use it--and if `mmap' doesn't work, fall back on doing
-the job in another way using `read' and `write'.
+ The proper way to use 'mmap' is to try it on the specific file for
+which you want to use it--and if 'mmap' doesn't work, fall back on doing
+the job in another way using 'read' and 'write'.
The reason this precaution is needed is that the GNU kernel (the
HURD) provides a user-extensible file system, in which there can be many
-different kinds of "ordinary files". Many of them support `mmap', but
+different kinds of "ordinary files". Many of them support 'mmap', but
some do not. It is important to make programs handle all these kinds of
files.
@@ -2886,8 +2886,8 @@
makes it possible to produce a good quality formatted book, using TeX,
and to generate an Info file. It is also possible to generate HTML
output from Texinfo source. See the Texinfo manual, either the
-hardcopy, or the on-line version available through `info' or the Emacs
-Info subsystem (`C-h i').
+hardcopy, or the on-line version available through 'info' or the Emacs
+Info subsystem ('C-h i').
Nowadays some other formats such as Docbook and Sgmltexi can be
converted automatically into Texinfo. It is ok to produce the Texinfo
@@ -2921,9 +2921,9 @@
understand.
Instead, each manual should cover a coherent _topic_. For example,
-instead of a manual for `diff' and a manual for `diff3', we have one
+instead of a manual for 'diff' and a manual for 'diff3', we have one
manual for "comparison of files" which covers both of those programs, as
-well as `cmp'. By documenting these programs together, we can make the
+well as 'cmp'. By documenting these programs together, we can make the
whole subject clearer.
The manual which discusses a program should certainly document all of
@@ -2981,8 +2981,8 @@
computer program. Please use "invalid" for this, and reserve the term
"illegal" for activities prohibited by law.
- Please do not write `()' after a function name just to indicate it is
-a function. `foo ()' is not a function, it is a function call with no
+ Please do not write '()' after a function name just to indicate it is
+a function. 'foo ()' is not a function, it is a function call with no
arguments.
6.2 Doc Strings and Manuals
@@ -3022,17 +3022,17 @@
number for the manual in both of these places.
Each program documented in the manual should have a node named
-`PROGRAM Invocation' or `Invoking PROGRAM'. This node (together with
+'PROGRAM Invocation' or 'Invoking PROGRAM'. This node (together with
its subnodes, if any) should describe the program's command line
arguments and how to run it (the sort of information people would look
-for in a man page). Start with an address@hidden' containing a template for
+for in a man page). Start with an '@example' containing a template for
all the options and arguments that the program uses.
Alternatively, put a menu item in some menu whose item name fits one
of the above patterns. This identifies the node which that item points
to as the node for this purpose, regardless of the node's actual name.
- The `--usage' feature of the Info reader looks for such a node or
+ The '--usage' feature of the Info reader looks for such a node or
menu item in order to find the relevant text, so it is essential for
every Texinfo file to have one.
@@ -3048,7 +3048,7 @@
collection. For a single short document, you can use a very permissive
non-copyleft license, to avoid taking up space with a long license.
- See `http://www.gnu.org/copyleft/fdl-howto.html' for more explanation
+ See 'http://www.gnu.org/copyleft/fdl-howto.html' for more explanation
of how to employ the GFDL.
Note that it is not obligatory to include a copy of the GNU GPL or
@@ -3073,7 +3073,7 @@
of these manuals, the on-line versions of the manual should mention at
the very start that the printed manual is available and should point at
information for getting it--for instance, with a link to the page
-`http://www.gnu.org/order/order.html'. This should not be included in
+'http://www.gnu.org/order/order.html'. This should not be included in
the printed manual, though, because there it is redundant.
It is also useful to explain in the on-line forms of the manual how
@@ -3082,15 +3082,15 @@
6.7 The NEWS File
=================
-In addition to its manual, the package should have a file named `NEWS'
+In addition to its manual, the package should have a file named 'NEWS'
which contains a list of user-visible changes worth mentioning. In each
new release, add items to the front of the file and identify the version
they pertain to. Don't discard old items; leave them in the file after
the newer items. This way, a user upgrading from any previous version
can see what is new.
- If the `NEWS' file gets very long, move some of the older items into
-a file named `ONEWS' and put a note at the end referring the user to
+ If the 'NEWS' file gets very long, move some of the older items into
+a file named 'ONEWS' and put a note at the end referring the user to
that file.
6.8 Change Logs
@@ -3113,15 +3113,15 @@
tell them what is in it. What they want from a change log is a clear
explanation of how the earlier version differed.
- The change log file is normally called `ChangeLog' and covers an
+ The change log file is normally called 'ChangeLog' and covers an
entire directory. Each directory can have its own change log, or a
directory can use the change log of its parent directory--it's up to
you.
Another alternative is to record change log information with a
version control system such as RCS or CVS. This can be converted
-automatically to a `ChangeLog' file using `rcs2log'; in Emacs, the
-command `C-x v a' (`vc-update-change-log') does the job.
+automatically to a 'ChangeLog' file using 'rcs2log'; in Emacs, the
+command 'C-x v a' ('vc-update-change-log') does the job.
There's no need to describe the full purpose of the changes or how
they work together. However, sometimes it is useful to write one line
@@ -3138,8 +3138,8 @@
advised that it is a good idea to include them, for the sake of
copyright records.
- The easiest way to add an entry to `ChangeLog' is with the Emacs
-command `M-x add-change-log-entry'. An entry should have an asterisk,
+ The easiest way to add an entry to 'ChangeLog' is with the Emacs
+command 'M-x add-change-log-entry'. An entry should have an asterisk,
the name of the changed file, and then in parentheses the name of the
changed functions, variables or whatever, followed by a colon. Then
describe the changes you made to that function or variable.
@@ -3174,9 +3174,9 @@
they won't find it when they search.
For example, some people are tempted to abbreviate groups of function
-names by writing `* register.el ({insert,jump-to}-register)'; this is
-not a good idea, since searching for `jump-to-register' or
-`insert-register' would not find that entry.
+names by writing '* register.el ({insert,jump-to}-register)'; this is
+not a good idea, since searching for 'jump-to-register' or
+'insert-register' would not find that entry.
Separate unrelated change log entries with blank lines. When two
entries represent parts of the same change, so that they work together,
@@ -3184,7 +3184,7 @@
name and the asterisk when successive entries are in the same file.
Break long lists of function names by closing continued lines with
-`)', rather than `,', and opening the continuation with `(' as in this
+')', rather than ',', and opening the continuation with '(' as in this
example:
* keyboard.c (menu_bar_items, tool_bar_items)
@@ -3242,9 +3242,9 @@
Source files can often contain code that is conditional to build-time or
static conditions. For example, C programs can contain compile-time
-`#if' conditionals; programs implemented in interpreted languages can
+'#if' conditionals; programs implemented in interpreted languages can
contain module imports of function definitions that are only performed
-for certain versions of the interpreter; and Automake `Makefile.am'
+for certain versions of the interpreter; and Automake 'Makefile.am'
files can contain variable definitions or target declarations that are
only to be considered if a configure-time Automake conditional is true.
@@ -3272,14 +3272,14 @@
self-evident.
Next, here is an entry describing a new definition which is entirely
-conditional: the C macro `FRAME_WINDOW_P' is defined (and used) only
-when the macro `HAVE_X_WINDOWS' is defined:
+conditional: the C macro 'FRAME_WINDOW_P' is defined (and used) only
+when the macro 'HAVE_X_WINDOWS' is defined:
* frame.h [HAVE_X_WINDOWS] (FRAME_WINDOW_P): Macro defined.
- Next, an entry for a change within the function `init_display', whose
+ Next, an entry for a change within the function 'init_display', whose
definition as a whole is unconditional, but the changes themselves are
-contained in a `#ifdef HAVE_LIBNCURSES' conditional:
+contained in a '#ifdef HAVE_LIBNCURSES' conditional:
* dispnew.c (init_display) [HAVE_LIBNCURSES]: If X, call tgetent.
@@ -3293,8 +3293,8 @@
Indicate the part of a function which changed by using angle brackets
enclosing an indication of what the changed part does. Here is an entry
-for a change in the part of the function `sh-while-getopts' that deals
-with `sh' commands:
+for a change in the part of the function 'sh-while-getopts' that deals
+with 'sh' commands:
* progmodes/sh-script.el (sh-while-getopts) <sh>: Handle case that
user-specified option string is empty.
@@ -3339,8 +3339,8 @@
Manuals::).
Finally, the GNU help2man program
-(`http://www.gnu.org/software/help2man/') is one way to automate
-generation of a man page, in this case from `--help' output. This is
+('http://www.gnu.org/software/help2man/') is one way to automate
+generation of a man page, in this case from '--help' output. This is
sufficient in many cases.
6.10 Reading other Manuals
@@ -3372,65 +3372,65 @@
7.1 How Configuration Should Work
=================================
-Each GNU distribution should come with a shell script named `configure'.
+Each GNU distribution should come with a shell script named 'configure'.
This script is given arguments which describe the kind of machine and
-system you want to compile the program for. The `configure' script must
+system you want to compile the program for. The 'configure' script must
record the configuration options so that they affect compilation.
The description here is the specification of the interface for the
-`configure' script in GNU packages. Many packages implement it using
+'configure' script in GNU packages. Many packages implement it using
GNU Autoconf (*note Introduction: (autoconf)Top.) and/or GNU Automake
(*note Introduction: (automake)Top.), but you do not have to use these
tools. You can implement it any way you like; for instance, by making
-`configure' be a wrapper around a completely different configuration
+'configure' be a wrapper around a completely different configuration
system.
- Another way for the `configure' script to operate is to make a link
-from a standard name such as `config.h' to the proper configuration file
+ Another way for the 'configure' script to operate is to make a link
+from a standard name such as 'config.h' to the proper configuration file
for the chosen system. If you use this technique, the distribution
-should _not_ contain a file named `config.h'. This is so that people
+should _not_ contain a file named 'config.h'. This is so that people
won't be able to build the program without configuring it first.
- Another thing that `configure' can do is to edit the Makefile. If
+ Another thing that 'configure' can do is to edit the Makefile. If
you do this, the distribution should _not_ contain a file named
-`Makefile'. Instead, it should include a file `Makefile.in' which
+'Makefile'. Instead, it should include a file 'Makefile.in' which
contains the input used for editing. Once again, this is so that people
won't be able to build the program without configuring it first.
- If `configure' does write the `Makefile', then `Makefile' should have
-a target named `Makefile' which causes `configure' to be rerun, setting
+ If 'configure' does write the 'Makefile', then 'Makefile' should have
+a target named 'Makefile' which causes 'configure' to be rerun, setting
up the same configuration that was set up last time. The files that
-`configure' reads should be listed as dependencies of `Makefile'.
+'configure' reads should be listed as dependencies of 'Makefile'.
- All the files which are output from the `configure' script should
+ All the files which are output from the 'configure' script should
have comments at the beginning explaining that they were generated
-automatically using `configure'. This is so that users won't think of
+automatically using 'configure'. This is so that users won't think of
trying to edit them by hand.
- The `configure' script should write a file named `config.status'
+ The 'configure' script should write a file named 'config.status'
which describes which configuration options were specified when the
program was last configured. This file should be a shell script which,
if run, will recreate the same configuration.
- The `configure' script should accept an option of the form
-`--srcdir=DIRNAME' to specify the directory where sources are found (if
+ The 'configure' script should accept an option of the form
+'--srcdir=DIRNAME' to specify the directory where sources are found (if
it is not the current directory). This makes it possible to build the
program in a separate directory, so that the actual source directory is
not modified.
- If the user does not specify `--srcdir', then `configure' should
-check both `.' and `..' to see if it can find the sources. If it finds
+ If the user does not specify '--srcdir', then 'configure' should
+check both '.' and '..' to see if it can find the sources. If it finds
the sources in one of these places, it should use them from there.
Otherwise, it should report that it cannot find the sources, and should
exit with nonzero status.
- Usually the easy way to support `--srcdir' is by editing a definition
-of `VPATH' into the Makefile. Some rules may need to refer explicitly
-to the specified source directory. To make this possible, `configure'
-can add to the Makefile a variable named `srcdir' whose value is
+ Usually the easy way to support '--srcdir' is by editing a definition
+of 'VPATH' into the Makefile. Some rules may need to refer explicitly
+to the specified source directory. To make this possible, 'configure'
+can add to the Makefile a variable named 'srcdir' whose value is
precisely the specified directory.
- In addition, the `configure' script should take options corresponding
+ In addition, the 'configure' script should take options corresponding
to most of the standard directory variables (*note Directory
Variables::). Here is the list:
@@ -3439,79 +3439,79 @@
--datarootdir --datadir --infodir --localedir --mandir --docdir
--htmldir --dvidir --pdfdir --psdir
- The `configure' script should also take an argument which specifies
+ The 'configure' script should also take an argument which specifies
the type of system to build the program for. This argument should look
like this:
CPU-COMPANY-SYSTEM
For example, an Athlon-based GNU/Linux system might be
-`i686-pc-linux-gnu'.
+'i686-pc-linux-gnu'.
- The `configure' script needs to be able to decode all plausible
-alternatives for how to describe a machine. Thus, `athlon-pc-gnu/linux'
-would be a valid alias. There is a shell script called `config.sub'
+ The 'configure' script needs to be able to decode all plausible
+alternatives for how to describe a machine. Thus, 'athlon-pc-gnu/linux'
+would be a valid alias. There is a shell script called 'config.sub'
(http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.sub;hb=HEAD)
that you can use as a subroutine to validate system types and
canonicalize aliases.
- The `configure' script should also take the option
-`--build=BUILDTYPE', which should be equivalent to a plain BUILDTYPE
-argument. For example, `configure --build=i686-pc-linux-gnu' is
-equivalent to `configure i686-pc-linux-gnu'. When the build type is not
-specified by an option or argument, the `configure' script should
-normally guess it using the shell script `config.guess'
+ The 'configure' script should also take the option
+'--build=BUILDTYPE', which should be equivalent to a plain BUILDTYPE
+argument. For example, 'configure --build=i686-pc-linux-gnu' is
+equivalent to 'configure i686-pc-linux-gnu'. When the build type is not
+specified by an option or argument, the 'configure' script should
+normally guess it using the shell script 'config.guess'
(http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.guess;hb=HEAD).
Other options are permitted to specify in more detail the software or
hardware present on the machine, to include or exclude optional parts of
the package, or to adjust the name of some tools or arguments to them:
-`--enable-FEATURE[=PARAMETER]'
+'--enable-FEATURE[=PARAMETER]'
Configure the package to build and install an optional user-level
facility called FEATURE. This allows users to choose which
- optional features to include. Giving an optional PARAMETER of `no'
+ optional features to include. Giving an optional PARAMETER of 'no'
should omit FEATURE, if it is built by default.
- No `--enable' option should *ever* cause one feature to replace
- another. No `--enable' option should ever substitute one useful
+ No '--enable' option should *ever* cause one feature to replace
+ another. No '--enable' option should ever substitute one useful
behavior for another useful behavior. The only proper use for
- `--enable' is for questions of whether to build part of the program
+ '--enable' is for questions of whether to build part of the program
or exclude it.
-`--with-PACKAGE'
+'--with-PACKAGE'
The package PACKAGE will be installed, so configure this package to
work with PACKAGE.
- Possible values of PACKAGE include `gnu-as' (or `gas'), `gnu-ld',
- `gnu-libc', `gdb', `x', and `x-toolkit'.
+ Possible values of PACKAGE include 'gnu-as' (or 'gas'), 'gnu-ld',
+ 'gnu-libc', 'gdb', 'x', and 'x-toolkit'.
- Do not use a `--with' option to specify the file name to use to
- find certain files. That is outside the scope of what `--with'
+ Do not use a '--with' option to specify the file name to use to
+ find certain files. That is outside the scope of what '--with'
options are for.
-`VARIABLE=VALUE'
+'VARIABLE=VALUE'
Set the value of the variable VARIABLE to VALUE. This is used to
override the default values of commands or arguments in the build
- process. For example, the user could issue `configure CFLAGS=-g
+ process. For example, the user could issue 'configure CFLAGS=-g
CXXFLAGS=-g' to build with debugging information and without the
default optimization.
- Specifying variables as arguments to `configure', like this:
+ Specifying variables as arguments to 'configure', like this:
./configure CC=gcc
is preferable to setting them in environment variables:
CC=gcc ./configure
as it helps to recreate the same configuration later with
- `config.status'. However, both methods should be supported.
+ 'config.status'. However, both methods should be supported.
- All `configure' scripts should accept all of the "detail" options and
+ All 'configure' scripts should accept all of the "detail" options and
the variable settings, whether or not they make any difference to the
particular package at hand. In particular, they should accept any
-option that starts with `--with-' or `--enable-'. This is so users will
+option that starts with '--with-' or '--enable-'. This is so users will
be able to configure an entire GNU source tree at once with a single set
of options.
- You will note that the categories `--with-' and `--enable-' are
+ You will note that the categories '--with-' and '--enable-' are
narrow: they *do not* provide a place for any sort of option you might
think of. That is deliberate. We want to limit the possible
configuration options in GNU software. We do not want GNU programs to
@@ -3521,29 +3521,29 @@
cross-compilation. In such a case, the host and target machines for the
program may be different.
- The `configure' script should normally treat the specified type of
+ The 'configure' script should normally treat the specified type of
system as both the host and the target, thus producing a program which
works for the same type of machine that it runs on.
To compile a program to run on a host type that differs from the
-build type, use the configure option `--host=HOSTTYPE', where HOSTTYPE
+build type, use the configure option '--host=HOSTTYPE', where HOSTTYPE
uses the same syntax as BUILDTYPE. The host type normally defaults to
the build type.
To configure a cross-compiler, cross-assembler, or what have you, you
should specify a target different from the host, using the configure
-option `--target=TARGETTYPE'. The syntax for TARGETTYPE is the same as
+option '--target=TARGETTYPE'. The syntax for TARGETTYPE is the same as
for the host type. So the command would look like this:
./configure --host=HOSTTYPE --target=TARGETTYPE
The target type normally defaults to the host type. Programs for
-which cross-operation is not meaningful need not accept the `--target'
+which cross-operation is not meaningful need not accept the '--target'
option, because configuring an entire operating system for
cross-operation is not a meaningful operation.
Some programs have ways of configuring themselves automatically. If
-your program is set up to do this, your `configure' script can simply
+your program is set up to do this, your 'configure' script can simply
ignore most of its arguments.
7.2 Makefile Conventions
@@ -3561,11 +3561,11 @@
SHELL = /bin/sh
-to avoid trouble on systems where the `SHELL' variable might be
+to avoid trouble on systems where the 'SHELL' variable might be
inherited from the environment. (This is never a problem with GNU
-`make'.)
+'make'.)
- Different `make' programs have incompatible suffix lists and implicit
+ Different 'make' programs have incompatible suffix lists and implicit
rules, and this sometimes creates confusion or misbehavior. So it is a
good idea to set the suffix list explicitly using only the suffixes you
need in the particular Makefile, like this:
@@ -3576,27 +3576,27 @@
The first line clears out the suffix list, the second introduces all
suffixes which may be subject to implicit rules in this Makefile.
- Don't assume that `.' is in the path for command execution. When you
+ Don't assume that '.' is in the path for command execution. When you
need to run programs that are a part of your package during the make,
-please make sure that it uses `./' if the program is built as part of
-the make or `$(srcdir)/' if the file is an unchanging part of the source
+please make sure that it uses './' if the program is built as part of
+the make or '$(srcdir)/' if the file is an unchanging part of the source
code. Without one of these prefixes, the current search path is used.
- The distinction between `./' (the "build directory") and `$(srcdir)/'
+ The distinction between './' (the "build directory") and '$(srcdir)/'
(the "source directory") is important because users can build in a
-separate directory using the `--srcdir' option to `configure'. A rule
+separate directory using the '--srcdir' option to 'configure'. A rule
of the form:
foo.1 : foo.man sedscript
sed -f sedscript foo.man > foo.1
will fail when the build directory is not the source directory, because
-`foo.man' and `sedscript' are in the source directory.
+'foo.man' and 'sedscript' are in the source directory.
- When using GNU `make', relying on `VPATH' to find the source file
+ When using GNU 'make', relying on 'VPATH' to find the source file
will work in the case where there is a single dependency file, since the
-`make' automatic variable `$<' will represent the source file wherever
-it is. (Many versions of `make' set `$<' only in implicit rules.) A
+'make' automatic variable '$<' will represent the source file wherever
+it is. (Many versions of 'make' set '$<' only in implicit rules.) A
Makefile target like
foo.o : bar.c
@@ -3607,9 +3607,9 @@
foo.o : bar.c
$(CC) -I. -I$(srcdir) $(CFLAGS) -c $< -o $@
-in order to allow `VPATH' to work correctly. When the target has
-multiple dependencies, using an explicit `$(srcdir)' is the easiest way
-to make the rule work well. For example, the target above for `foo.1'
+in order to allow 'VPATH' to work correctly. When the target has
+multiple dependencies, using an explicit '$(srcdir)' is the easiest way
+to make the rule work well. For example, the target above for 'foo.1'
is best written as:
foo.1 : foo.man sedscript
@@ -3628,26 +3628,26 @@
in any way.
Try to make the build and installation targets, at least (and all
-their subtargets) work correctly with a parallel `make'.
+their subtargets) work correctly with a parallel 'make'.
7.2.2 Utilities in Makefiles
----------------------------
-Write the Makefile commands (and any shell scripts, such as `configure')
-to run under `sh' (both the traditional Bourne shell and the POSIX
-shell), not `csh'. Don't use any special features of `ksh' or `bash',
-or POSIX features not widely supported in traditional Bourne `sh'.
+Write the Makefile commands (and any shell scripts, such as 'configure')
+to run under 'sh' (both the traditional Bourne shell and the POSIX
+shell), not 'csh'. Don't use any special features of 'ksh' or 'bash',
+or POSIX features not widely supported in traditional Bourne 'sh'.
- The `configure' script and the Makefile rules for building and
+ The 'configure' script and the Makefile rules for building and
installation should not use any utilities directly except these:
awk cat cmp cp diff echo egrep expr false grep install-info ln ls
mkdir mv printf pwd rm rmdir sed sleep sort tar test touch tr true
- Compression programs such as `gzip' can be used in the `dist' rule.
+ Compression programs such as 'gzip' can be used in the 'dist' rule.
Generally, stick to the widely-supported (usually POSIX-specified)
-options and features of these programs. For example, don't use `mkdir
+options and features of these programs. For example, don't use 'mkdir
-p', convenient as it may be, because a few systems don't support it at
all and with others, it is not safe for parallel execution. For a list
of known incompatibilities, see *note Portable Shell Programming:
@@ -3657,23 +3657,23 @@
since a few file systems don't support them.
The Makefile rules for building and installation can also use
-compilers and related programs, but should do so via `make' variables so
+compilers and related programs, but should do so via 'make' variables so
that the user can substitute alternatives. Here are some of the
programs we mean:
ar bison cc flex install ld ldconfig lex
make makeinfo ranlib texi2dvi yacc
- Use the following `make' variables to run those programs:
+ Use the following 'make' variables to run those programs:
$(AR) $(BISON) $(CC) $(FLEX) $(INSTALL) $(LD) $(LDCONFIG) $(LEX)
$(MAKE) $(MAKEINFO) $(RANLIB) $(TEXI2DVI) $(YACC)
- When you use `ranlib' or `ldconfig', you should make sure nothing bad
+ When you use 'ranlib' or 'ldconfig', you should make sure nothing bad
happens if the system does not have the program in question. Arrange to
ignore an error from that command, and print a message before the
command to tell the user that failure of this command does not mean a
-problem. (The Autoconf `AC_PROG_RANLIB' macro can help with this.)
+problem. (The Autoconf 'AC_PROG_RANLIB' macro can help with this.)
If you use symbolic links, you should implement a fallback for
systems that don't have symbolic links.
@@ -3693,28 +3693,28 @@
options, and so on.
In particular, you should run most utility programs via variables.
-Thus, if you use Bison, have a variable named `BISON' whose default
-value is set with `BISON = bison', and refer to it with `$(BISON)'
+Thus, if you use Bison, have a variable named 'BISON' whose default
+value is set with 'BISON = bison', and refer to it with '$(BISON)'
whenever you need to use Bison.
- File management utilities such as `ln', `rm', `mv', and so on, need
+ File management utilities such as 'ln', 'rm', 'mv', and so on, need
not be referred to through variables in this way, since users don't need
to replace them with other programs.
Each program-name variable should come with an options variable that
-is used to supply options to the program. Append `FLAGS' to the
+is used to supply options to the program. Append 'FLAGS' to the
program-name variable name to get the options variable name--for
-example, `BISONFLAGS'. (The names `CFLAGS' for the C compiler, `YFLAGS'
-for yacc, and `LFLAGS' for lex, are exceptions to this rule, but we keep
-them because they are standard.) Use `CPPFLAGS' in any compilation
-command that runs the preprocessor, and use `LDFLAGS' in any compilation
-command that does linking as well as in any direct use of `ld'.
+example, 'BISONFLAGS'. (The names 'CFLAGS' for the C compiler, 'YFLAGS'
+for yacc, and 'LFLAGS' for lex, are exceptions to this rule, but we keep
+them because they are standard.) Use 'CPPFLAGS' in any compilation
+command that runs the preprocessor, and use 'LDFLAGS' in any compilation
+command that does linking as well as in any direct use of 'ld'.
If there are C compiler options that _must_ be used for proper
-compilation of certain files, do not include them in `CFLAGS'. Users
-expect to be able to specify `CFLAGS' freely themselves. Instead,
+compilation of certain files, do not include them in 'CFLAGS'. Users
+expect to be able to specify 'CFLAGS' freely themselves. Instead,
arrange to pass the necessary options to the C compiler independently of
-`CFLAGS', by writing them explicitly in the compilation commands or by
+'CFLAGS', by writing them explicitly in the compilation commands or by
defining an implicit rule, like this:
CFLAGS = -g
@@ -3722,25 +3722,25 @@
.c.o:
$(CC) -c $(CPPFLAGS) $(ALL_CFLAGS) $<
- Do include the `-g' option in `CFLAGS', because that is not
+ Do include the '-g' option in 'CFLAGS', because that is not
_required_ for proper compilation. You can consider it a default that
is only recommended. If the package is set up so that it is compiled
-with GCC by default, then you might as well include `-O' in the default
-value of `CFLAGS' as well.
+with GCC by default, then you might as well include '-O' in the default
+value of 'CFLAGS' as well.
- Put `CFLAGS' last in the compilation command, after other variables
-containing compiler options, so the user can use `CFLAGS' to override
+ Put 'CFLAGS' last in the compilation command, after other variables
+containing compiler options, so the user can use 'CFLAGS' to override
the others.
- `CFLAGS' should be used in every invocation of the C compiler, both
+ 'CFLAGS' should be used in every invocation of the C compiler, both
those which do compilation and those which do linking.
- Every Makefile should define the variable `INSTALL', which is the
+ Every Makefile should define the variable 'INSTALL', which is the
basic command for installing a file into the system.
- Every Makefile should also define the variables `INSTALL_PROGRAM' and
-`INSTALL_DATA'. (The default for `INSTALL_PROGRAM' should be
-`$(INSTALL)'; the default for `INSTALL_DATA' should be `${INSTALL} -m
+ Every Makefile should also define the variables 'INSTALL_PROGRAM' and
+'INSTALL_DATA'. (The default for 'INSTALL_PROGRAM' should be
+'$(INSTALL)'; the default for 'INSTALL_DATA' should be '${INSTALL} -m
644'.) Then it should use those variables as the commands for actual
installation, for executables and non-executables respectively. Minimal
use of these variables is as follows:
@@ -3748,7 +3748,7 @@
$(INSTALL_PROGRAM) foo $(bindir)/foo
$(INSTALL_DATA) libfoo.a $(libdir)/libfoo.a
- However, it is preferable to support a `DESTDIR' prefix on the target
+ However, it is preferable to support a 'DESTDIR' prefix on the target
files, as explained in the next section.
It is acceptable, but not required, to install multiple files in one
@@ -3756,48 +3756,48 @@
$(INSTALL_PROGRAM) foo bar baz $(bindir)
-7.2.4 `DESTDIR': Support for Staged Installs
+7.2.4 'DESTDIR': Support for Staged Installs
--------------------------------------------
-`DESTDIR' is a variable prepended to each installed target file, like
+'DESTDIR' is a variable prepended to each installed target file, like
this:
$(INSTALL_PROGRAM) foo $(DESTDIR)$(bindir)/foo
$(INSTALL_DATA) libfoo.a $(DESTDIR)$(libdir)/libfoo.a
- The `DESTDIR' variable is specified by the user on the `make' command
+ The 'DESTDIR' variable is specified by the user on the 'make' command
line as an absolute file name. For example:
make DESTDIR=/tmp/stage install
-`DESTDIR' should be supported only in the `install*' and `uninstall*'
+'DESTDIR' should be supported only in the 'install*' and 'uninstall*'
targets, as those are the only targets where it is useful.
- If your installation step would normally install `/usr/local/bin/foo'
-and `/usr/local/lib/libfoo.a', then an installation invoked as in the
-example above would install `/tmp/stage/usr/local/bin/foo' and
-`/tmp/stage/usr/local/lib/libfoo.a' instead.
+ If your installation step would normally install '/usr/local/bin/foo'
+and '/usr/local/lib/libfoo.a', then an installation invoked as in the
+example above would install '/tmp/stage/usr/local/bin/foo' and
+'/tmp/stage/usr/local/lib/libfoo.a' instead.
- Prepending the variable `DESTDIR' to each target in this way provides
+ Prepending the variable 'DESTDIR' to each target in this way provides
for "staged installs", where the installed files are not placed directly
into their expected location but are instead copied into a temporary
-location (`DESTDIR'). However, installed files maintain their relative
+location ('DESTDIR'). However, installed files maintain their relative
directory structure and any embedded file names will not be modified.
- You should not set the value of `DESTDIR' in your `Makefile' at all;
+ You should not set the value of 'DESTDIR' in your 'Makefile' at all;
then the files are installed into their expected locations by default.
-Also, specifying `DESTDIR' should not change the operation of the
+Also, specifying 'DESTDIR' should not change the operation of the
software in any way, so its value should not be included in any file
contents.
- `DESTDIR' support is commonly used in package creation. It is also
+ 'DESTDIR' support is commonly used in package creation. It is also
helpful to users who want to understand what a given package will
install where, and to allow users who don't normally have permissions to
install into protected areas to build and install before gaining those
-permissions. Finally, it can be useful with tools such as `stow', where
+permissions. Finally, it can be useful with tools such as 'stow', where
code is installed in one place but made to appear to be installed
somewhere else using symbolic links or special mount operations. So, we
-strongly recommend GNU packages support `DESTDIR', though it is not an
+strongly recommend GNU packages support 'DESTDIR', though it is not an
absolute requirement.
7.2.5 Variables for Installation Directories
@@ -3809,8 +3809,8 @@
below. They are based on a standard file system layout; variants of it
are used in GNU/Linux and other modern operating systems.
- Installers are expected to override these values when calling `make'
-(e.g., `make prefix=/usr install' or `configure' (e.g., `configure
+ Installers are expected to override these values when calling 'make'
+(e.g., 'make prefix=/usr install' or 'configure' (e.g., 'configure
--prefix=/usr'). GNU packages should not try to guess which value
should be appropriate for these variables on the system they are being
installed onto: use the default settings specified here so that all GNU
@@ -3825,58 +3825,58 @@
two, and nothing should be directly installed into these two
directories.
-`prefix'
+'prefix'
A prefix used in constructing the default values of the variables
- listed below. The default value of `prefix' should be
- `/usr/local'. When building the complete GNU system, the prefix
- will be empty and `/usr' will be a symbolic link to `/'. (If you
- are using Autoconf, write it as address@hidden@'.)
+ listed below. The default value of 'prefix' should be
+ '/usr/local'. When building the complete GNU system, the prefix
+ will be empty and '/usr' will be a symbolic link to '/'. (If you
+ are using Autoconf, write it as '@prefix@'.)
- Running `make install' with a different value of `prefix' from the
+ Running 'make install' with a different value of 'prefix' from the
one used to build the program should _not_ recompile the program.
-`exec_prefix'
+'exec_prefix'
A prefix used in constructing the default values of some of the
- variables listed below. The default value of `exec_prefix' should
- be `$(prefix)'. (If you are using Autoconf, write it as
- address@hidden@'.)
+ variables listed below. The default value of 'exec_prefix' should
+ be '$(prefix)'. (If you are using Autoconf, write it as
+ '@exec_prefix@'.)
- Generally, `$(exec_prefix)' is used for directories that contain
+ Generally, '$(exec_prefix)' is used for directories that contain
machine-specific files (such as executables and subroutine
- libraries), while `$(prefix)' is used directly for other
+ libraries), while '$(prefix)' is used directly for other
directories.
- Running `make install' with a different value of `exec_prefix' from
+ Running 'make install' with a different value of 'exec_prefix' from
the one used to build the program should _not_ recompile the
program.
Executable programs are installed in one of the following
directories.
-`bindir'
+'bindir'
The directory for installing executable programs that users can
- run. This should normally be `/usr/local/bin', but write it as
- `$(exec_prefix)/bin'. (If you are using Autoconf, write it as
- address@hidden@'.)
+ run. This should normally be '/usr/local/bin', but write it as
+ '$(exec_prefix)/bin'. (If you are using Autoconf, write it as
+ '@bindir@'.)
-`sbindir'
+'sbindir'
The directory for installing executable programs that can be run
from the shell, but are only generally useful to system
- administrators. This should normally be `/usr/local/sbin', but
- write it as `$(exec_prefix)/sbin'. (If you are using Autoconf,
- write it as address@hidden@'.)
+ administrators. This should normally be '/usr/local/sbin', but
+ write it as '$(exec_prefix)/sbin'. (If you are using Autoconf,
+ write it as '@sbindir@'.)
-`libexecdir'
+'libexecdir'
The directory for installing executable programs to be run by other
programs rather than by users. This directory should normally be
- `/usr/local/libexec', but write it as `$(exec_prefix)/libexec'.
- (If you are using Autoconf, write it as address@hidden@'.)
+ '/usr/local/libexec', but write it as '$(exec_prefix)/libexec'.
+ (If you are using Autoconf, write it as '@libexecdir@'.)
- The definition of `libexecdir' is the same for all packages, so you
+ The definition of 'libexecdir' is the same for all packages, so you
should install your data in a subdirectory thereof. Most packages
- install their data under `$(libexecdir)/PACKAGE-NAME/', possibly
+ install their data under '$(libexecdir)/PACKAGE-NAME/', possibly
within additional subdirectories thereof, such as
- `$(libexecdir)/PACKAGE-NAME/MACHINE/VERSION'.
+ '$(libexecdir)/PACKAGE-NAME/MACHINE/VERSION'.
Data files used by the program during its execution are divided into
categories in two ways.
@@ -3897,192 +3897,192 @@
Here are the variables Makefiles should use to specify directories to
put these various kinds of files in:
-`datarootdir'
+'datarootdir'
The root of the directory tree for read-only
architecture-independent data files. This should normally be
- `/usr/local/share', but write it as `$(prefix)/share'. (If you are
- using Autoconf, write it as address@hidden@'.) `datadir''s default
- value is based on this variable; so are `infodir', `mandir', and
+ '/usr/local/share', but write it as '$(prefix)/share'. (If you are
+ using Autoconf, write it as '@datarootdir@'.) 'datadir''s default
+ value is based on this variable; so are 'infodir', 'mandir', and
others.
-`datadir'
+'datadir'
The directory for installing idiosyncratic read-only
architecture-independent data files for this program. This is
- usually the same place as `datarootdir', but we use the two
+ usually the same place as 'datarootdir', but we use the two
separate variables so that you can move these program-specific
files without altering the location for Info files, man pages, etc.
- This should normally be `/usr/local/share', but write it as
- `$(datarootdir)'. (If you are using Autoconf, write it as
- address@hidden@'.)
+ This should normally be '/usr/local/share', but write it as
+ '$(datarootdir)'. (If you are using Autoconf, write it as
+ '@datadir@'.)
- The definition of `datadir' is the same for all packages, so you
+ The definition of 'datadir' is the same for all packages, so you
should install your data in a subdirectory thereof. Most packages
- install their data under `$(datadir)/PACKAGE-NAME/'.
+ install their data under '$(datadir)/PACKAGE-NAME/'.
-`sysconfdir'
+'sysconfdir'
The directory for installing read-only data files that pertain to a
single machine-that is to say, files for configuring a host.
- Mailer and network configuration files, `/etc/passwd', and so forth
+ Mailer and network configuration files, '/etc/passwd', and so forth
belong here. All the files in this directory should be ordinary
ASCII text files. This directory should normally be
- `/usr/local/etc', but write it as `$(prefix)/etc'. (If you are
- using Autoconf, write it as address@hidden@'.)
+ '/usr/local/etc', but write it as '$(prefix)/etc'. (If you are
+ using Autoconf, write it as '@sysconfdir@'.)
Do not install executables here in this directory (they probably
- belong in `$(libexecdir)' or `$(sbindir)'). Also do not install
+ belong in '$(libexecdir)' or '$(sbindir)'). Also do not install
files that are modified in the normal course of their use (programs
whose purpose is to change the configuration of the system
- excluded). Those probably belong in `$(localstatedir)'.
+ excluded). Those probably belong in '$(localstatedir)'.
-`sharedstatedir'
+'sharedstatedir'
The directory for installing architecture-independent data files
which the programs modify while they run. This should normally be
- `/usr/local/com', but write it as `$(prefix)/com'. (If you are
- using Autoconf, write it as address@hidden@'.)
+ '/usr/local/com', but write it as '$(prefix)/com'. (If you are
+ using Autoconf, write it as '@sharedstatedir@'.)
-`localstatedir'
+'localstatedir'
The directory for installing data files which the programs modify
while they run, and that pertain to one specific machine. Users
should never need to modify files in this directory to configure
the package's operation; put such configuration information in
- separate files that go in `$(datadir)' or `$(sysconfdir)'.
- `$(localstatedir)' should normally be `/usr/local/var', but write
- it as `$(prefix)/var'. (If you are using Autoconf, write it as
- address@hidden@'.)
+ separate files that go in '$(datadir)' or '$(sysconfdir)'.
+ '$(localstatedir)' should normally be '/usr/local/var', but write
+ it as '$(prefix)/var'. (If you are using Autoconf, write it as
+ '@localstatedir@'.)
These variables specify the directory for installing certain specific
types of files, if your program has them. Every GNU package should have
-Info files, so every program needs `infodir', but not all need `libdir'
-or `lispdir'.
+Info files, so every program needs 'infodir', but not all need 'libdir'
+or 'lispdir'.
-`includedir'
+'includedir'
The directory for installing header files to be included by user
- programs with the C `#include' preprocessor directive. This should
- normally be `/usr/local/include', but write it as
- `$(prefix)/include'. (If you are using Autoconf, write it as
- address@hidden@'.)
+ programs with the C '#include' preprocessor directive. This should
+ normally be '/usr/local/include', but write it as
+ '$(prefix)/include'. (If you are using Autoconf, write it as
+ '@includedir@'.)
Most compilers other than GCC do not look for header files in
- directory `/usr/local/include'. So installing the header files
+ directory '/usr/local/include'. So installing the header files
this way is only useful with GCC. Sometimes this is not a problem
because some libraries are only really intended to work with GCC.
But some libraries are intended to work with other compilers. They
should install their header files in two places, one specified by
- `includedir' and one specified by `oldincludedir'.
+ 'includedir' and one specified by 'oldincludedir'.
-`oldincludedir'
- The directory for installing `#include' header files for use with
- compilers other than GCC. This should normally be `/usr/include'.
- (If you are using Autoconf, you can write it as address@hidden@'.)
+'oldincludedir'
+ The directory for installing '#include' header files for use with
+ compilers other than GCC. This should normally be '/usr/include'.
+ (If you are using Autoconf, you can write it as '@oldincludedir@'.)
The Makefile commands should check whether the value of
- `oldincludedir' is empty. If it is, they should not try to use it;
+ 'oldincludedir' is empty. If it is, they should not try to use it;
they should cancel the second installation of the header files.
A package should not replace an existing header in this directory
unless the header came from the same package. Thus, if your Foo
- package provides a header file `foo.h', then it should install the
- header file in the `oldincludedir' directory if either (1) there is
- no `foo.h' there or (2) the `foo.h' that exists came from the Foo
+ package provides a header file 'foo.h', then it should install the
+ header file in the 'oldincludedir' directory if either (1) there is
+ no 'foo.h' there or (2) the 'foo.h' that exists came from the Foo
package.
- To tell whether `foo.h' came from the Foo package, put a magic
- string in the file--part of a comment--and `grep' for that string.
+ To tell whether 'foo.h' came from the Foo package, put a magic
+ string in the file--part of a comment--and 'grep' for that string.
-`docdir'
+'docdir'
The directory for installing documentation files (other than Info)
for this package. By default, it should be
- `/usr/local/share/doc/YOURPKG', but it should be written as
- `$(datarootdir)/doc/YOURPKG'. (If you are using Autoconf, write it
- as address@hidden@'.) The YOURPKG subdirectory, which may include a
+ '/usr/local/share/doc/YOURPKG', but it should be written as
+ '$(datarootdir)/doc/YOURPKG'. (If you are using Autoconf, write it
+ as '@docdir@'.) The YOURPKG subdirectory, which may include a
version number, prevents collisions among files with common names,
- such as `README'.
+ such as 'README'.
-`infodir'
+'infodir'
The directory for installing the Info files for this package. By
- default, it should be `/usr/local/share/info', but it should be
- written as `$(datarootdir)/info'. (If you are using Autoconf,
- write it as address@hidden@'.) `infodir' is separate from `docdir' for
+ default, it should be '/usr/local/share/info', but it should be
+ written as '$(datarootdir)/info'. (If you are using Autoconf,
+ write it as '@infodir@'.) 'infodir' is separate from 'docdir' for
compatibility with existing practice.
-`htmldir'
-`dvidir'
-`pdfdir'
-`psdir'
+'htmldir'
+'dvidir'
+'pdfdir'
+'psdir'
Directories for installing documentation files in the particular
- format. They should all be set to `$(docdir)' by default. (If you
- are using Autoconf, write them as address@hidden@', address@hidden@',
etc.)
+ format. They should all be set to '$(docdir)' by default. (If you
+ are using Autoconf, write them as '@htmldir@', '@dvidir@', etc.)
Packages which supply several translations of their documentation
- should install them in `$(htmldir)/'LL, `$(pdfdir)/'LL, etc. where
- LL is a locale abbreviation such as `en' or `pt_BR'.
+ should install them in '$(htmldir)/'LL, '$(pdfdir)/'LL, etc. where
+ LL is a locale abbreviation such as 'en' or 'pt_BR'.
-`libdir'
+'libdir'
The directory for object files and libraries of object code. Do
not install executables here, they probably ought to go in
- `$(libexecdir)' instead. The value of `libdir' should normally be
- `/usr/local/lib', but write it as `$(exec_prefix)/lib'. (If you
- are using Autoconf, write it as address@hidden@'.)
+ '$(libexecdir)' instead. The value of 'libdir' should normally be
+ '/usr/local/lib', but write it as '$(exec_prefix)/lib'. (If you
+ are using Autoconf, write it as '@libdir@'.)
-`lispdir'
+'lispdir'
The directory for installing any Emacs Lisp files in this package.
- By default, it should be `/usr/local/share/emacs/site-lisp', but it
- should be written as `$(datarootdir)/emacs/site-lisp'.
+ By default, it should be '/usr/local/share/emacs/site-lisp', but it
+ should be written as '$(datarootdir)/emacs/site-lisp'.
- If you are using Autoconf, write the default as address@hidden@'. In
- order to make address@hidden@' work, you need the following lines in
- your `configure.in' file:
+ If you are using Autoconf, write the default as '@lispdir@'. In
+ order to make '@lispdir@' work, you need the following lines in
+ your 'configure.in' file:
lispdir='${datarootdir}/emacs/site-lisp'
AC_SUBST(lispdir)
-`localedir'
+'localedir'
The directory for installing locale-specific message catalogs for
- this package. By default, it should be `/usr/local/share/locale',
- but it should be written as `$(datarootdir)/locale'. (If you are
- using Autoconf, write it as address@hidden@'.) This directory usually
+ this package. By default, it should be '/usr/local/share/locale',
+ but it should be written as '$(datarootdir)/locale'. (If you are
+ using Autoconf, write it as '@localedir@'.) This directory usually
has a subdirectory per locale.
Unix-style man pages are installed in one of the following:
-`mandir'
+'mandir'
The top-level directory for installing the man pages (if any) for
- this package. It will normally be `/usr/local/share/man', but you
- should write it as `$(datarootdir)/man'. (If you are using
- Autoconf, write it as address@hidden@'.)
+ this package. It will normally be '/usr/local/share/man', but you
+ should write it as '$(datarootdir)/man'. (If you are using
+ Autoconf, write it as '@mandir@'.)
-`man1dir'
+'man1dir'
The directory for installing section 1 man pages. Write it as
- `$(mandir)/man1'.
-`man2dir'
+ '$(mandir)/man1'.
+'man2dir'
The directory for installing section 2 man pages. Write it as
- `$(mandir)/man2'
-`...'
+ '$(mandir)/man2'
+'...'
*Don't make the primary documentation for any GNU software be a man
page. Write a manual in Texinfo instead. Man pages are just for
the sake of people running GNU software on Unix, which is a
secondary application only.*
-`manext'
+'manext'
The file name extension for the installed man page. This should
contain a period followed by the appropriate digit; it should
- normally be `.1'.
+ normally be '.1'.
-`man1ext'
+'man1ext'
The file name extension for installed section 1 man pages.
-`man2ext'
+'man2ext'
The file name extension for installed section 2 man pages.
-`...'
- Use these names instead of `manext' if the package needs to install
+'...'
+ Use these names instead of 'manext' if the package needs to install
man pages in more than one section of the manual.
And finally, you should set the following variable:
-`srcdir'
+'srcdir'
The directory for the sources being compiled. The value of this
- variable is normally inserted by the `configure' shell script. (If
- you are using Autoconf, use `srcdir = @srcdir@'.)
+ variable is normally inserted by the 'configure' shell script. (If
+ you are using Autoconf, use 'srcdir = @srcdir@'.)
For example:
@@ -4102,7 +4102,7 @@
If your program installs a large number of files into one of the
standard user-specified directories, it might be useful to group them
into a subdirectory particular to that program. If you do this, you
-should write the `install' rule to create these subdirectories.
+should write the 'install' rule to create these subdirectories.
Do not expect the user to include the subdirectory name in the value
of any of the variables listed above. The idea of having a uniform set
@@ -4124,19 +4124,19 @@
All GNU programs should have the following targets in their Makefiles:
-`all'
+'all'
Compile the entire program. This should be the default target.
This target need not rebuild any documentation files; Info files
should normally be included in the distribution, and DVI (and other
documentation format) files should be made only when explicitly
asked for.
- By default, the Make rules should compile and link with `-g', so
+ By default, the Make rules should compile and link with '-g', so
that executable programs have debugging symbols. Otherwise, you
are essentially helpless in the face of a crash, and it is often
far from easy to reproduce with a fresh build.
-`install'
+'install'
Compile the program and copy the executables, libraries, and so on
to the file names where they should reside for actual use. If
there is a simple test to verify that a program is properly
@@ -4146,33 +4146,33 @@
debugging that may be needed later, and nowadays disk space is
cheap and dynamic loaders typically ensure debug sections are not
loaded during normal execution. Users that need stripped binaries
- may invoke the `install-strip' target to do that.
+ may invoke the 'install-strip' target to do that.
- If possible, write the `install' target rule so that it does not
+ If possible, write the 'install' target rule so that it does not
modify anything in the directory where the program was built,
- provided `make all' has just been done. This is convenient for
+ provided 'make all' has just been done. This is convenient for
building the program under one user name and installing it under
another.
The commands should create all the directories in which files are
to be installed, if they don't already exist. This includes the
- directories specified as the values of the variables `prefix' and
- `exec_prefix', as well as all subdirectories that are needed. One
- way to do this is by means of an `installdirs' target as described
+ directories specified as the values of the variables 'prefix' and
+ 'exec_prefix', as well as all subdirectories that are needed. One
+ way to do this is by means of an 'installdirs' target as described
below.
- Use `-' before any command for installing a man page, so that
- `make' will ignore any errors. This is in case there are systems
+ Use '-' before any command for installing a man page, so that
+ 'make' will ignore any errors. This is in case there are systems
that don't have the Unix man page documentation system installed.
- The way to install Info files is to copy them into `$(infodir)'
- with `$(INSTALL_DATA)' (*note Command Variables::), and then run
- the `install-info' program if it is present. `install-info' is a
- program that edits the Info `dir' file to add or update the menu
+ The way to install Info files is to copy them into '$(infodir)'
+ with '$(INSTALL_DATA)' (*note Command Variables::), and then run
+ the 'install-info' program if it is present. 'install-info' is a
+ program that edits the Info 'dir' file to add or update the menu
entry for the given Info file; it is part of the Texinfo package.
Here is a sample rule to install an Info file that also tries to
- handle some additional situations, such as `install-info' not being
+ handle some additional situations, such as 'install-info' not being
present.
do-install-info: foo.info installdirs
@@ -4194,36 +4194,36 @@
"$(DESTDIR)$(infodir)/foo.info"; \
else true; fi
- When writing the `install' target, you must classify all the
+ When writing the 'install' target, you must classify all the
commands into three categories: normal ones, "pre-installation"
commands and "post-installation" commands. *Note Install Command
Categories::.
-`install-html'
-`install-dvi'
-`install-pdf'
-`install-ps'
+'install-html'
+'install-dvi'
+'install-pdf'
+'install-ps'
These targets install documentation in formats other than Info;
they're intended to be called explicitly by the person installing
the package, if that format is desired. GNU prefers Info files, so
- these must be installed by the `install' target.
+ these must be installed by the 'install' target.
When you have many documentation files to install, we recommend
that you avoid collisions and clutter by arranging for these
targets to install in subdirectories of the appropriate
- installation directory, such as `htmldir'. As one example, if your
+ installation directory, such as 'htmldir'. As one example, if your
package has multiple manuals, and you wish to install HTML
documentation with many files (such as the "split" mode output by
- `makeinfo --html'), you'll certainly want to use subdirectories, or
+ 'makeinfo --html'), you'll certainly want to use subdirectories, or
two nodes with the same name in different manuals will overwrite
each other.
- Please make these `install-FORMAT' targets invoke the commands for
+ Please make these 'install-FORMAT' targets invoke the commands for
the FORMAT target, for example, by making FORMAT a dependency.
-`uninstall'
- Delete all the installed files--the copies that the `install' and
- `install-*' targets create.
+'uninstall'
+ Delete all the installed files--the copies that the 'install' and
+ 'install-*' targets create.
This rule should not modify the directories where compilation is
done, only the directories where files are installed.
@@ -4232,9 +4232,9 @@
like the installation commands. *Note Install Command
Categories::.
-`install-strip'
- Like `install', but strip the executable files while installing
- them. In simple cases, this target can use the `install' target in
+'install-strip'
+ Like 'install', but strip the executable files while installing
+ them. In simple cases, this target can use the 'install' target in
a simple way:
install-strip:
@@ -4242,10 +4242,10 @@
install
But if the package installs scripts as well as real executables,
- the `install-strip' target can't just refer to the `install'
+ the 'install-strip' target can't just refer to the 'install'
target; it has to strip the executables but not the scripts.
- `install-strip' should not strip the executables in the build
+ 'install-strip' should not strip the executables in the build
directory which are being copied for installation. It should only
strip the copies that are installed.
@@ -4254,67 +4254,67 @@
install a stripped executable for actual execution while saving the
unstripped executable elsewhere in case there is a bug.
-`clean'
+'clean'
Delete all files in the current directory that are normally created
by building the program. Also delete files in other directories if
they are created by this makefile. However, don't delete the files
that record the configuration. Also preserve files that could be
made by building, but normally aren't because the distribution
comes with them. There is no need to delete parent directories
- that were created with `mkdir -p', since they could have existed
+ that were created with 'mkdir -p', since they could have existed
anyway.
- Delete `.dvi' files here if they are not part of the distribution.
+ Delete '.dvi' files here if they are not part of the distribution.
-`distclean'
+'distclean'
Delete all files in the current directory (or created by this
makefile) that are created by configuring or building the program.
If you have unpacked the source and built the program without
- creating any other files, `make distclean' should leave only the
+ creating any other files, 'make distclean' should leave only the
files that were in the distribution. However, there is no need to
- delete parent directories that were created with `mkdir -p', since
+ delete parent directories that were created with 'mkdir -p', since
they could have existed anyway.
-`mostlyclean'
- Like `clean', but may refrain from deleting a few files that people
- normally don't want to recompile. For example, the `mostlyclean'
- target for GCC does not delete `libgcc.a', because recompiling it
+'mostlyclean'
+ Like 'clean', but may refrain from deleting a few files that people
+ normally don't want to recompile. For example, the 'mostlyclean'
+ target for GCC does not delete 'libgcc.a', because recompiling it
is rarely necessary and takes a lot of time.
-`maintainer-clean'
+'maintainer-clean'
Delete almost everything that can be reconstructed with this
Makefile. This typically includes everything deleted by
- `distclean', plus more: C source files produced by Bison, tags
+ 'distclean', plus more: C source files produced by Bison, tags
tables, Info files, and so on.
The reason we say "almost everything" is that running the command
- `make maintainer-clean' should not delete `configure' even if
- `configure' can be remade using a rule in the Makefile. More
- generally, `make maintainer-clean' should not delete anything that
- needs to exist in order to run `configure' and then begin to build
+ 'make maintainer-clean' should not delete 'configure' even if
+ 'configure' can be remade using a rule in the Makefile. More
+ generally, 'make maintainer-clean' should not delete anything that
+ needs to exist in order to run 'configure' and then begin to build
the program. Also, there is no need to delete parent directories
- that were created with `mkdir -p', since they could have existed
- anyway. These are the only exceptions; `maintainer-clean' should
+ that were created with 'mkdir -p', since they could have existed
+ anyway. These are the only exceptions; 'maintainer-clean' should
delete everything else that can be rebuilt.
- The `maintainer-clean' target is intended to be used by a
+ The 'maintainer-clean' target is intended to be used by a
maintainer of the package, not by ordinary users. You may need
- special tools to reconstruct some of the files that `make
+ special tools to reconstruct some of the files that 'make
maintainer-clean' deletes. Since these files are normally included
in the distribution, we don't take care to make them easy to
reconstruct. If you find you need to unpack the full distribution
again, don't blame us.
To help make users aware of this, the commands for the special
- `maintainer-clean' target should start with these two:
+ 'maintainer-clean' target should start with these two:
@echo 'This command is intended for maintainers to use; it'
@echo 'deletes files that may need special tools to rebuild.'
-`TAGS'
+'TAGS'
Update a tags table for this program.
-`info'
+'info'
Generate any Info files needed. The best way to write the rules is
as follows:
@@ -4323,8 +4323,8 @@
foo.info: foo.texi chap1.texi chap2.texi
$(MAKEINFO) $(srcdir)/foo.texi
- You must define the variable `MAKEINFO' in the Makefile. It should
- run the `makeinfo' program, which is part of the Texinfo
+ You must define the variable 'MAKEINFO' in the Makefile. It should
+ run the 'makeinfo' program, which is part of the Texinfo
distribution.
Normally a GNU distribution comes with Info files, and that means
@@ -4333,14 +4333,14 @@
directory. When users build the package, ordinarily Make will not
update the Info files because they will already be up to date.
-`dvi'
-`html'
-`pdf'
-`ps'
+'dvi'
+'html'
+'pdf'
+'ps'
Generate documentation files in the given format. These targets
should always exist, but any or all can be a no-op if the given
output format cannot be generated. These targets should not be
- dependencies of the `all' target; the user must manually invoke
+ dependencies of the 'all' target; the user must manually invoke
them.
Here's an example rule for generating DVI files from Texinfo:
@@ -4350,11 +4350,11 @@
foo.dvi: foo.texi chap1.texi chap2.texi
$(TEXI2DVI) $(srcdir)/foo.texi
- You must define the variable `TEXI2DVI' in the Makefile. It should
- run the program `texi2dvi', which is part of the Texinfo
- distribution. (`texi2dvi' uses TeX to do the real work of
+ You must define the variable 'TEXI2DVI' in the Makefile. It should
+ run the program 'texi2dvi', which is part of the Texinfo
+ distribution. ('texi2dvi' uses TeX to do the real work of
formatting. TeX is not distributed with Texinfo.) Alternatively,
- write only the dependencies, and allow GNU `make' to provide the
+ write only the dependencies, and allow GNU 'make' to provide the
command.
Here's another example, this one for generating HTML from Texinfo:
@@ -4364,32 +4364,32 @@
foo.html: foo.texi chap1.texi chap2.texi
$(TEXI2HTML) $(srcdir)/foo.texi
- Again, you would define the variable `TEXI2HTML' in the Makefile;
- for example, it might run `makeinfo --no-split --html' (`makeinfo'
+ Again, you would define the variable 'TEXI2HTML' in the Makefile;
+ for example, it might run 'makeinfo --no-split --html' ('makeinfo'
is part of the Texinfo distribution).
-`dist'
+'dist'
Create a distribution tar file for this program. The tar file
should be set up so that the file names in the tar file start with
a subdirectory name which is the name of the package it is a
distribution for. This name can include the version number.
For example, the distribution tar file of GCC version 1.40 unpacks
- into a subdirectory named `gcc-1.40'.
+ into a subdirectory named 'gcc-1.40'.
The easiest way to do this is to create a subdirectory
- appropriately named, use `ln' or `cp' to install the proper files
- in it, and then `tar' that subdirectory.
+ appropriately named, use 'ln' or 'cp' to install the proper files
+ in it, and then 'tar' that subdirectory.
- Compress the tar file with `gzip'. For example, the actual
- distribution file for GCC version 1.40 is called `gcc-1.40.tar.gz'.
+ Compress the tar file with 'gzip'. For example, the actual
+ distribution file for GCC version 1.40 is called 'gcc-1.40.tar.gz'.
It is ok to support other free compression formats as well.
- The `dist' target should explicitly depend on all non-source files
+ The 'dist' target should explicitly depend on all non-source files
that are in the distribution, to make sure they are up to date in
the distribution. *Note Making Releases: Releases.
-`check'
+'check'
Perform self-tests (if any). The user must build the program
before running the tests, but need not install the program; you
should write the self-tests so that they work when the program is
@@ -4398,15 +4398,15 @@
The following targets are suggested as conventional names, for
programs in which they are useful.
-`installcheck'
+'installcheck'
Perform installation tests (if any). The user must build and
install the program before running the tests. You should not
- assume that `$(bindir)' is in the search path.
+ assume that '$(bindir)' is in the search path.
-`installdirs'
- It's useful to add a target named `installdirs' to create the
+'installdirs'
+ It's useful to add a target named 'installdirs' to create the
directories where files are installed, and their parent
- directories. There is a script called `mkinstalldirs' which is
+ directories. There is a script called 'mkinstalldirs' which is
convenient for this; you can find it in the Gnulib package. You
can use a rule like this:
@@ -4417,7 +4417,7 @@
$(libdir) $(infodir) \
$(mandir)
- or, if you wish to support `DESTDIR' (strongly encouraged),
+ or, if you wish to support 'DESTDIR' (strongly encouraged),
# Make sure all installation directories (e.g. $(bindir))
# actually exist by making them if necessary.
@@ -4433,7 +4433,7 @@
7.2.7 Install Command Categories
--------------------------------
-When writing the `install' target, you must classify all the commands
+When writing the 'install' target, you must classify all the commands
into three categories: normal ones, "pre-installation" commands and
"post-installation" commands.
@@ -4450,7 +4450,7 @@
normal commands.
The most common use for a post-installation command is to run
-`install-info'. This cannot be done with a normal command, since it
+'install-info'. This cannot be done with a normal command, since it
alters a file (the Info directory) which does not come entirely and
solely from the package being installed. It is a post-installation
command because it needs to be done after the normal command which
@@ -4459,7 +4459,7 @@
Most programs don't need any pre-installation commands, but we have
the feature just in case it is needed.
- To classify the commands in the `install' rule into these three
+ To classify the commands in the 'install' rule into these three
categories, insert "category lines" among them. A category line
specifies the category for the commands that follow.
@@ -4477,12 +4477,12 @@
$(POST_INSTALL) # Post-install commands follow.
$(NORMAL_INSTALL) # Normal commands follow.
- If you don't use a category line at the beginning of the `install'
+ If you don't use a category line at the beginning of the 'install'
rule, all the commands are classified as normal until the first category
line. If you don't use any category lines, all the commands are
classified as normal.
- These are the category lines for `uninstall':
+ These are the category lines for 'uninstall':
$(PRE_UNINSTALL) # Pre-uninstall commands follow.
$(POST_UNINSTALL) # Post-uninstall commands follow.
@@ -4491,7 +4491,7 @@
Typically, a pre-uninstall command would be used for deleting entries
from the Info directory.
- If the `install' or `uninstall' target has any dependencies which act
+ If the 'install' or 'uninstall' target has any dependencies which act
as subroutines of installation, then you should start _each_
dependency's commands with a category line, and start the main target's
commands with a category line also. This way, you can ensure that each
@@ -4516,7 +4516,7 @@
Programs to build binary packages work by extracting the
pre-installation and post-installation commands. Here is one way of
-extracting the pre-installation commands (the `-s' option to `make' is
+extracting the pre-installation commands (the '-s' option to 'make' is
needed to silence messages about entering subdirectories):
make -s -n install -o all \
@@ -4525,7 +4525,7 @@
NORMAL_INSTALL=normal-install \
| gawk -f pre-install.awk
-where the file `pre-install.awk' could contain this:
+where the file 'pre-install.awk' could contain this:
$0 ~ /^(normal-install|post-install)[ \t]*$/ {on = 0}
on {print $0}
@@ -4538,9 +4538,9 @@
version and a minor. We have no objection to using more than two
numbers, but it is very unlikely that you really need them.
- Package the distribution of `Foo version 69.96' up in a gzipped tar
-file with the name `foo-69.96.tar.gz'. It should unpack into a
-subdirectory named `foo-69.96'.
+ Package the distribution of 'Foo version 69.96' up in a gzipped tar
+file with the name 'foo-69.96.tar.gz'. It should unpack into a
+subdirectory named 'foo-69.96'.
Building and installing the program should never modify any of the
files contained in the distribution. This means that all the files that
@@ -4549,28 +4549,28 @@
never changed automatically; non-source files are produced from source
files by programs under the control of the Makefile.
- The distribution should contain a file named `README' which gives the
+ The distribution should contain a file named 'README' which gives the
name of the package, and a general description of what it does. It is
also good to explain the purpose of each of the first-level
-subdirectories in the package, if there are any. The `README' file
+subdirectories in the package, if there are any. The 'README' file
should either state the version number of the package, or refer to where
in the package it can be found.
- The `README' file should refer to the file `INSTALL', which should
+ The 'README' file should refer to the file 'INSTALL', which should
contain an explanation of the installation procedure.
- The `README' file should also refer to the file which contains the
+ The 'README' file should also refer to the file which contains the
copying conditions. The GNU GPL, if used, should be in a file called
-`COPYING'. If the GNU LGPL is used, it should be in a file called
-`COPYING.LESSER'.
+'COPYING'. If the GNU LGPL is used, it should be in a file called
+'COPYING.LESSER'.
Naturally, all the source files must be in the distribution. It is
okay to include non-source files in the distribution along with the
source files they are generated from, provided they are up-to-date with
the source they are made from, and machine-independent, so that normal
building of the distribution will never modify them. We commonly
-include non-source files produced by Autoconf, Automake, Bison, `lex',
-TeX, and `makeinfo'; this helps avoid unnecessary dependencies between
+include non-source files produced by Autoconf, Automake, Bison, 'lex',
+TeX, and 'makeinfo'; this helps avoid unnecessary dependencies between
our distributions, so that users can install whichever packages they
want to install.
@@ -4583,7 +4583,7 @@
and that directories are world-readable and world-searchable (octal mode
755). We used to recommend that all directories in the distribution
also be world-writable (octal mode 777), because ancient versions of
-`tar' would otherwise not cope when extracting the archive as an
+'tar' would otherwise not cope when extracting the archive as an
unprivileged user. That can easily lead to security issues when
creating the archive, however, so now we recommend against that.
@@ -4596,12 +4596,12 @@
Try to make sure that all the file names will be unique on MS-DOS. A
name on MS-DOS consists of up to 8 characters, optionally followed by a
period and up to three characters. MS-DOS will truncate extra
-characters both before and after the period. Thus, `foobarhacker.c' and
-`foobarhacker.o' are not ambiguous; they are truncated to `foobarha.c'
-and `foobarha.o', which are distinct.
+characters both before and after the period. Thus, 'foobarhacker.c' and
+'foobarhacker.o' are not ambiguous; they are truncated to 'foobarha.c'
+and 'foobarha.o', which are distinct.
- Include in your distribution a copy of the `texinfo.tex' you used to
-test print any `*.texinfo' or `*.texi' files.
+ Include in your distribution a copy of the 'texinfo.tex' you used to
+test print any '*.texinfo' or '*.texi' files.
Likewise, if your program uses small GNU software packages like
regex, getopt, obstack, or termcap, include them in the distribution
@@ -4621,13 +4621,13 @@
is ethical.
The GNU definition of free software is found on the GNU web site at
-`http://www.gnu.org/philosophy/free-sw.html', and the definition of free
-documentation is found at `http://www.gnu.org/philosophy/free-doc.html'.
+'http://www.gnu.org/philosophy/free-sw.html', and the definition of free
+documentation is found at 'http://www.gnu.org/philosophy/free-doc.html'.
The terms "free" and "non-free", used in this document, refer to those
definitions.
A list of important licenses and whether they qualify as free is in
-`http://www.gnu.org/licenses/license-list.html'. If it is not clear
+'http://www.gnu.org/licenses/license-list.html'. If it is not clear
whether a license qualifies as free, please ask the GNU Project by
writing to <address@hidden>. We will answer, and if the license is
an important one, we will add it to the list.
@@ -4670,15 +4670,15 @@
software to run.
Some free programs strongly encourage the use of non-free software.
-A typical example is `mplayer'. It is free software in itself, and the
-free code can handle some kinds of files. However, `mplayer' recommends
+A typical example is 'mplayer'. It is free software in itself, and the
+free code can handle some kinds of files. However, 'mplayer' recommends
use of non-free codecs for other kinds of files, and users that install
-`mplayer' are very likely to install those codecs along with it. To
-recommend `mplayer' is, in effect, to promote use of the non-free
+'mplayer' are very likely to install those codecs along with it. To
+recommend 'mplayer' is, in effect, to promote use of the non-free
codecs.
Thus, you should not recommend programs that strongly encourage the
-use of non-free software. This is why we do not list `mplayer' in the
+use of non-free software. This is why we do not list 'mplayer' in the
Free Software Directory.
A GNU package should not refer the user to any non-free documentation
@@ -4721,7 +4721,7 @@
Version 1.3, 3 November 2008
Copyright (C) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.
- `http://fsf.org/'
+ 'http://fsf.org/'
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
@@ -5118,7 +5118,7 @@
the GNU Free Documentation License from time to time. Such new
versions will be similar in spirit to the present version, but may
differ in detail to address new problems or concerns. See
- `http://www.gnu.org/copyleft/'.
+ 'http://www.gnu.org/copyleft/'.
Each version of the License is given a distinguishing version
number. If the Document specifies that a particular numbered
Index: standards.txt.gz
===================================================================
RCS file: /web/www/www/prep/standards/standards.txt.gz,v
retrieving revision 1.61
retrieving revision 1.62
diff -u -b -r1.61 -r1.62
Binary files /tmp/cvsaCjtlQ and /tmp/cvsMGzCWV differ
Index: html_node/CPU-Portability.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/CPU-Portability.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/CPU-Portability.html 12 Jan 2012 19:20:20 -0000 1.52
+++ html_node/CPU-Portability.html 11 Mar 2012 00:26:38 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: CPU Portability</title>
@@ -135,9 +135,8 @@
<p>
Next: <a href="System-Functions.html#System-Functions" accesskey="n"
rel="next">System Functions</a>, Previous: <a
href="System-Portability.html#System-Portability" accesskey="p"
rel="previous">System Portability</a>, Up: <a href="Writing-C.html#Writing-C"
accesskey="u" rel="up">Writing C</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
</div>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Change-Log-Concepts.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Change-Log-Concepts.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Change-Log-Concepts.html 12 Jan 2012 19:20:20 -0000 1.52
+++ html_node/Change-Log-Concepts.html 11 Mar 2012 00:26:40 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Change Log Concepts</title>
@@ -109,9 +109,8 @@
<p>
Next: <a href="Style-of-Change-Logs.html#Style-of-Change-Logs" accesskey="n"
rel="next">Style of Change Logs</a>, Up: <a href="Change-Logs.html#Change-Logs"
accesskey="u" rel="up">Change Logs</a> [<a
href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Change-Logs.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Change-Logs.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Change-Logs.html 12 Jan 2012 19:20:20 -0000 1.52
+++ html_node/Change-Logs.html 11 Mar 2012 00:26:41 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Change Logs</title>
@@ -89,9 +89,8 @@
</td></tr>
</table>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Character-Set.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Character-Set.html,v
retrieving revision 1.44
retrieving revision 1.45
diff -u -b -r1.44 -r1.45
--- html_node/Character-Set.html 12 Jan 2012 19:20:20 -0000 1.44
+++ html_node/Character-Set.html 11 Mar 2012 00:26:41 -0000 1.45
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Character Set</title>
@@ -85,9 +85,8 @@
be the best choice.
</p>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Command-Variables.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Command-Variables.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Command-Variables.html 12 Jan 2012 19:20:20 -0000 1.52
+++ html_node/Command-Variables.html 11 Mar 2012 00:26:41 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Command Variables</title>
@@ -147,9 +147,8 @@
<p>
Next: <a href="DESTDIR.html#DESTDIR" accesskey="n" rel="next">DESTDIR</a>,
Previous: <a href="Utilities-in-Makefiles.html#Utilities-in-Makefiles"
accesskey="p" rel="previous">Utilities in Makefiles</a>, Up: <a
href="Makefile-Conventions.html#Makefile-Conventions" accesskey="u"
rel="up">Makefile Conventions</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
</div>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Command_002dLine-Interfaces.html
===================================================================
RCS file:
/web/www/www/prep/standards/html_node/Command_002dLine-Interfaces.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Command_002dLine-Interfaces.html 12 Jan 2012 19:20:21 -0000
1.52
+++ html_node/Command_002dLine-Interfaces.html 11 Mar 2012 00:26:41 -0000
1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Command-Line Interfaces</title>
@@ -119,9 +119,8 @@
<p>
Next: <a
href="Dynamic-Plug_002dIn-Interfaces.html#Dynamic-Plug_002dIn-Interfaces"
accesskey="n" rel="next">Dynamic Plug-In Interfaces</a>, Previous: <a
href="Graphical-Interfaces.html#Graphical-Interfaces" accesskey="p"
rel="previous">Graphical Interfaces</a>, Up: <a
href="Program-Behavior.html#Program-Behavior" accesskey="u" rel="up">Program
Behavior</a> [<a href="index.html#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Comments.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Comments.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Comments.html 12 Jan 2012 19:20:21 -0000 1.52
+++ html_node/Comments.html 11 Mar 2012 00:26:42 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Comments</title>
@@ -161,9 +161,8 @@
<p>
Next: <a href="Syntactic-Conventions.html#Syntactic-Conventions" accesskey="n"
rel="next">Syntactic Conventions</a>, Previous: <a
href="Formatting.html#Formatting" accesskey="p" rel="previous">Formatting</a>,
Up: <a href="Writing-C.html#Writing-C" accesskey="u" rel="up">Writing C</a>
[<a href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Compatibility.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Compatibility.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Compatibility.html 12 Jan 2012 19:20:21 -0000 1.52
+++ html_node/Compatibility.html 11 Mar 2012 00:26:42 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Compatibility</title>
@@ -101,9 +101,8 @@
<p>Additional useful features are welcome regardless of whether
there is any precedent for them.
</p>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Conditional-Changes.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Conditional-Changes.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Conditional-Changes.html 12 Jan 2012 19:20:21 -0000 1.52
+++ html_node/Conditional-Changes.html 11 Mar 2012 00:26:42 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Conditional Changes</title>
@@ -132,9 +132,8 @@
<p>
Next: <a href="Indicating-the-Part-Changed.html#Indicating-the-Part-Changed"
accesskey="n" rel="next">Indicating the Part Changed</a>, Previous: <a
href="Simple-Changes.html#Simple-Changes" accesskey="p" rel="previous">Simple
Changes</a>, Up: <a href="Change-Logs.html#Change-Logs" accesskey="u"
rel="up">Change Logs</a> [<a href="index.html#SEC_Contents" title="Table
of contents" rel="contents">Contents</a>][<a href="Index.html#Index"
title="Index" rel="index">Index</a>]</p>
</div>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Conditional-Compilation.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Conditional-Compilation.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Conditional-Compilation.html 12 Jan 2012 19:20:21 -0000
1.52
+++ html_node/Conditional-Compilation.html 11 Mar 2012 00:26:43 -0000
1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Conditional Compilation</title>
@@ -113,9 +113,8 @@
#endif
</pre></div>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Configuration.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Configuration.html,v
retrieving revision 1.54
retrieving revision 1.55
diff -u -b -r1.54 -r1.55
--- html_node/Configuration.html 12 Jan 2012 19:20:21 -0000 1.54
+++ html_node/Configuration.html 11 Mar 2012 00:26:44 -0000 1.55
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Configuration</title>
@@ -275,9 +275,8 @@
<p>
Next: <a href="Makefile-Conventions.html#Makefile-Conventions" accesskey="n"
rel="next">Makefile Conventions</a>, Up: <a
href="Managing-Releases.html#Managing-Releases" accesskey="u" rel="up">Managing
Releases</a> [<a href="index.html#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Contributions.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Contributions.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Contributions.html 12 Jan 2012 19:20:21 -0000 1.52
+++ html_node/Contributions.html 11 Mar 2012 00:26:44 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Contributions</title>
@@ -116,9 +116,8 @@
<p>
Next: <a href="Trademarks.html#Trademarks" accesskey="n"
rel="next">Trademarks</a>, Previous: <a
href="Reading-Non_002dFree-Code.html#Reading-Non_002dFree-Code" accesskey="p"
rel="previous">Reading Non-Free Code</a>, Up: <a
href="Legal-Issues.html#Legal-Issues" accesskey="u" rel="up">Legal Issues</a>
[<a href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
-<p>
-</p>
+
</body>
</html>
Index: html_node/DESTDIR.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/DESTDIR.html,v
retrieving revision 1.41
retrieving revision 1.42
diff -u -b -r1.41 -r1.42
--- html_node/DESTDIR.html 12 Jan 2012 19:20:21 -0000 1.41
+++ html_node/DESTDIR.html 11 Mar 2012 00:26:44 -0000 1.42
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: DESTDIR</title>
@@ -125,9 +125,8 @@
<p>
Next: <a href="Directory-Variables.html#Directory-Variables" accesskey="n"
rel="next">Directory Variables</a>, Previous: <a
href="Command-Variables.html#Command-Variables" accesskey="p"
rel="previous">Command Variables</a>, Up: <a
href="Makefile-Conventions.html#Makefile-Conventions" accesskey="u"
rel="up">Makefile Conventions</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
</div>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Design-Advice.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Design-Advice.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Design-Advice.html 12 Jan 2012 19:20:21 -0000 1.52
+++ html_node/Design-Advice.html 11 Mar 2012 00:26:44 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Design Advice</title>
@@ -86,9 +86,8 @@
</td></tr>
</table>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Directory-Variables.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Directory-Variables.html,v
retrieving revision 1.55
retrieving revision 1.56
diff -u -b -r1.55 -r1.56
--- html_node/Directory-Variables.html 12 Jan 2012 19:20:21 -0000 1.55
+++ html_node/Directory-Variables.html 11 Mar 2012 00:26:45 -0000 1.56
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Directory Variables</title>
@@ -441,9 +441,8 @@
<p>
Next: <a href="Standard-Targets.html#Standard-Targets" accesskey="n"
rel="next">Standard Targets</a>, Previous: <a href="DESTDIR.html#DESTDIR"
accesskey="p" rel="previous">DESTDIR</a>, Up: <a
href="Makefile-Conventions.html#Makefile-Conventions" accesskey="u"
rel="up">Makefile Conventions</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
</div>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Doc-Strings-and-Manuals.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Doc-Strings-and-Manuals.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Doc-Strings-and-Manuals.html 12 Jan 2012 19:20:21 -0000
1.52
+++ html_node/Doc-Strings-and-Manuals.html 11 Mar 2012 00:26:45 -0000
1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Doc Strings and Manuals</title>
@@ -91,9 +91,8 @@
<p>The only good way to use documentation strings in writing a good manual
is to use them as a source of information for writing good text.
</p>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Documentation.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Documentation.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Documentation.html 12 Jan 2012 19:20:21 -0000 1.52
+++ html_node/Documentation.html 11 Mar 2012 00:26:45 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Documentation</title>
@@ -97,9 +97,8 @@
</td></tr>
</table>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Dynamic-Plug_002dIn-Interfaces.html
===================================================================
RCS file:
/web/www/www/prep/standards/html_node/Dynamic-Plug_002dIn-Interfaces.html,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- html_node/Dynamic-Plug_002dIn-Interfaces.html 12 Jan 2012 19:20:22
-0000 1.11
+++ html_node/Dynamic-Plug_002dIn-Interfaces.html 11 Mar 2012 00:26:45
-0000 1.12
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Dynamic Plug-In Interfaces</title>
@@ -106,9 +106,8 @@
<p>
Next: <a href="Option-Table.html#Option-Table" accesskey="n" rel="next">Option
Table</a>, Previous: <a
href="Command_002dLine-Interfaces.html#Command_002dLine-Interfaces"
accesskey="p" rel="previous">Command-Line Interfaces</a>, Up: <a
href="Program-Behavior.html#Program-Behavior" accesskey="u" rel="up">Program
Behavior</a> [<a href="index.html#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Errors.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Errors.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Errors.html 12 Jan 2012 19:20:22 -0000 1.52
+++ html_node/Errors.html 11 Mar 2012 00:26:45 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Errors</title>
@@ -150,9 +150,8 @@
<p>
Next: <a href="User-Interfaces.html#User-Interfaces" accesskey="n"
rel="next">User Interfaces</a>, Previous: <a href="Libraries.html#Libraries"
accesskey="p" rel="previous">Libraries</a>, Up: <a
href="Program-Behavior.html#Program-Behavior" accesskey="u" rel="up">Program
Behavior</a> [<a href="index.html#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
-<p>
-</p>
+
</body>
</html>
Index: html_node/File-Usage.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/File-Usage.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/File-Usage.html 12 Jan 2012 19:20:22 -0000 1.52
+++ html_node/File-Usage.html 11 Mar 2012 00:26:45 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: File Usage</title>
@@ -81,9 +81,8 @@
is reasonable for the program to store other files in the same
directory.
</p>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Formatting.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Formatting.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Formatting.html 12 Jan 2012 19:20:22 -0000 1.52
+++ html_node/Formatting.html 11 Mar 2012 00:26:45 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Formatting</title>
@@ -217,9 +217,8 @@
<p>
Next: <a href="Comments.html#Comments" accesskey="n" rel="next">Comments</a>,
Up: <a href="Writing-C.html#Writing-C" accesskey="u" rel="up">Writing C</a>
[<a href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
-<p>
-</p>
+
</body>
</html>
Index: html_node/GNU-Free-Documentation-License.html
===================================================================
RCS file:
/web/www/www/prep/standards/html_node/GNU-Free-Documentation-License.html,v
retrieving revision 1.54
retrieving revision 1.55
diff -u -b -r1.54 -r1.55
--- html_node/GNU-Free-Documentation-License.html 12 Jan 2012 19:20:22
-0000 1.54
+++ html_node/GNU-Free-Documentation-License.html 11 Mar 2012 00:26:45
-0000 1.55
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: GNU Free Documentation License</title>
@@ -537,15 +537,13 @@
to permit their use in free software.
</p>
-
<hr>
<div class="header">
<p>
Next: <a href="Index.html#Index" accesskey="n" rel="next">Index</a>, Previous:
<a href="References.html#References" accesskey="p"
rel="previous">References</a>, Up: <a href="index.html#Top" accesskey="u"
rel="up">Top</a> [<a href="index.html#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
-<p>
-</p>
+
</body>
</html>
Index: html_node/GNU-Manuals.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/GNU-Manuals.html,v
retrieving revision 1.53
retrieving revision 1.54
diff -u -b -r1.53 -r1.54
--- html_node/GNU-Manuals.html 12 Jan 2012 19:20:22 -0000 1.53
+++ html_node/GNU-Manuals.html 11 Mar 2012 00:26:46 -0000 1.54
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: GNU Manuals</title>
@@ -178,9 +178,8 @@
<p>
Next: <a href="Doc-Strings-and-Manuals.html#Doc-Strings-and-Manuals"
accesskey="n" rel="next">Doc Strings and Manuals</a>, Up: <a
href="Documentation.html#Documentation" accesskey="u"
rel="up">Documentation</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
</div>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Graphical-Interfaces.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Graphical-Interfaces.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Graphical-Interfaces.html 12 Jan 2012 19:20:22 -0000 1.52
+++ html_node/Graphical-Interfaces.html 11 Mar 2012 00:26:46 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Graphical Interfaces</title>
@@ -95,9 +95,8 @@
the graphical interface, these won’t be much extra work.
</p>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Index.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Index.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Index.html 12 Jan 2012 19:20:22 -0000 1.52
+++ html_node/Index.html 11 Mar 2012 00:26:46 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Index</title>
@@ -385,9 +385,8 @@
<p>
Previous: <a
href="GNU-Free-Documentation-License.html#GNU-Free-Documentation-License"
accesskey="p" rel="previous">GNU Free Documentation License</a>, Up: <a
href="index.html#Top" accesskey="u" rel="up">Top</a> [<a
href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="#Index" title="Index"
rel="index">Index</a>]</p>
</div>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Indicating-the-Part-Changed.html
===================================================================
RCS file:
/web/www/www/prep/standards/html_node/Indicating-the-Part-Changed.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Indicating-the-Part-Changed.html 12 Jan 2012 19:20:22 -0000
1.52
+++ html_node/Indicating-the-Part-Changed.html 11 Mar 2012 00:26:46 -0000
1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Indicating the Part Changed</title>
@@ -78,9 +78,8 @@
</pre></div>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Install-Command-Categories.html
===================================================================
RCS file:
/web/www/www/prep/standards/html_node/Install-Command-Categories.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Install-Command-Categories.html 12 Jan 2012 19:20:22 -0000
1.52
+++ html_node/Install-Command-Categories.html 11 Mar 2012 00:26:46 -0000
1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Install Command Categories</title>
@@ -183,9 +183,8 @@
<p>
Previous: <a href="Standard-Targets.html#Standard-Targets" accesskey="p"
rel="previous">Standard Targets</a>, Up: <a
href="Makefile-Conventions.html#Makefile-Conventions" accesskey="u"
rel="up">Makefile Conventions</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
</div>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Internationalization.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Internationalization.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Internationalization.html 12 Jan 2012 19:20:22 -0000 1.52
+++ html_node/Internationalization.html 11 Mar 2012 00:26:46 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Internationalization</title>
@@ -188,9 +188,8 @@
<p>
Next: <a href="Character-Set.html#Character-Set" accesskey="n"
rel="next">Character Set</a>, Previous: <a
href="System-Functions.html#System-Functions" accesskey="p"
rel="previous">System Functions</a>, Up: <a href="Writing-C.html#Writing-C"
accesskey="u" rel="up">Writing C</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
</div>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Legal-Issues.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Legal-Issues.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Legal-Issues.html 12 Jan 2012 19:20:22 -0000 1.52
+++ html_node/Legal-Issues.html 11 Mar 2012 00:26:47 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Legal Issues</title>
@@ -80,9 +80,8 @@
</td></tr>
</table>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Libraries.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Libraries.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Libraries.html 12 Jan 2012 19:20:22 -0000 1.52
+++ html_node/Libraries.html 11 Mar 2012 00:26:47 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Libraries</title>
@@ -94,9 +94,8 @@
<p>Static functions and variables can be used as you like and need not
fit any naming convention.
</p>
-<p>
-</p>
+
</body>
</html>
Index: html_node/License-for-Manuals.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/License-for-Manuals.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/License-for-Manuals.html 12 Jan 2012 19:20:23 -0000 1.52
+++ html_node/License-for-Manuals.html 11 Mar 2012 00:26:48 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: License for Manuals</title>
@@ -83,9 +83,8 @@
short manual, whose size would be increased considerably by including
the program’s license, it is probably better not to include it.
</p>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Makefile-Basics.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Makefile-Basics.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Makefile-Basics.html 12 Jan 2012 19:20:23 -0000 1.52
+++ html_node/Makefile-Basics.html 11 Mar 2012 00:26:48 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Makefile Basics</title>
@@ -158,9 +158,8 @@
<p>
Next: <a href="Utilities-in-Makefiles.html#Utilities-in-Makefiles"
accesskey="n" rel="next">Utilities in Makefiles</a>, Up: <a
href="Makefile-Conventions.html#Makefile-Conventions" accesskey="u"
rel="up">Makefile Conventions</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
</div>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Makefile-Conventions.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Makefile-Conventions.html,v
retrieving revision 1.55
retrieving revision 1.56
diff -u -b -r1.55 -r1.56
--- html_node/Makefile-Conventions.html 12 Jan 2012 19:20:23 -0000 1.55
+++ html_node/Makefile-Conventions.html 11 Mar 2012 00:26:48 -0000 1.56
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Makefile Conventions</title>
@@ -96,9 +96,8 @@
</td></tr>
</table>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Man-Pages.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Man-Pages.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Man-Pages.html 12 Jan 2012 19:20:23 -0000 1.52
+++ html_node/Man-Pages.html 11 Mar 2012 00:26:49 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Man Pages</title>
@@ -115,9 +115,8 @@
<p>
Next: <a href="Reading-other-Manuals.html#Reading-other-Manuals" accesskey="n"
rel="next">Reading other Manuals</a>, Previous: <a
href="Change-Logs.html#Change-Logs" accesskey="p" rel="previous">Change
Logs</a>, Up: <a href="Documentation.html#Documentation" accesskey="u"
rel="up">Documentation</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
</div>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Managing-Releases.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Managing-Releases.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Managing-Releases.html 12 Jan 2012 19:20:23 -0000 1.52
+++ html_node/Managing-Releases.html 11 Mar 2012 00:26:49 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Managing Releases</title>
@@ -85,9 +85,8 @@
</td></tr>
</table>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Manual-Credits.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Manual-Credits.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Manual-Credits.html 12 Jan 2012 19:20:23 -0000 1.52
+++ html_node/Manual-Credits.html 11 Mar 2012 00:26:49 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Manual Credits</title>
@@ -73,9 +73,8 @@
the company in a suitable place in the manual, but do not cite the
company as an author.
</p>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Manual-Structure-Details.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Manual-Structure-Details.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Manual-Structure-Details.html 12 Jan 2012 19:20:23 -0000
1.52
+++ html_node/Manual-Structure-Details.html 11 Mar 2012 00:26:49 -0000
1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Manual Structure Details</title>
@@ -93,9 +93,8 @@
<p>If one manual describes several programs, it should have such a node for
each program described in the manual.
</p>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Memory-Usage.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Memory-Usage.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Memory-Usage.html 12 Jan 2012 19:20:23 -0000 1.52
+++ html_node/Memory-Usage.html 11 Mar 2012 00:26:49 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Memory Usage</title>
@@ -92,9 +92,8 @@
free it simply to silence such a tool.
</p>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Mmap.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Mmap.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Mmap.html 12 Jan 2012 19:20:23 -0000 1.52
+++ html_node/Mmap.html 11 Mar 2012 00:26:49 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Mmap</title>
@@ -82,9 +82,8 @@
all these kinds of files.
</p>
-<p>
-</p>
+
</body>
</html>
Index: html_node/NEWS-File.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/NEWS-File.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/NEWS-File.html 12 Jan 2012 19:20:23 -0000 1.52
+++ html_node/NEWS-File.html 11 Mar 2012 00:26:49 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: NEWS File</title>
@@ -79,9 +79,8 @@
into a file named ‘<tt>ONEWS</tt>’ and put a note at the end
referring the
user to that file.
</p>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Names.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Names.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Names.html 12 Jan 2012 19:20:23 -0000 1.52
+++ html_node/Names.html 11 Mar 2012 00:26:50 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Names</title>
@@ -122,9 +122,8 @@
<p>
Next: <a href="System-Portability.html#System-Portability" accesskey="n"
rel="next">System Portability</a>, Previous: <a
href="Syntactic-Conventions.html#Syntactic-Conventions" accesskey="p"
rel="previous">Syntactic Conventions</a>, Up: <a
href="Writing-C.html#Writing-C" accesskey="u" rel="up">Writing C</a> [<a
href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Non_002dGNU-Standards.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Non_002dGNU-Standards.html,v
retrieving revision 1.42
retrieving revision 1.43
diff -u -b -r1.42 -r1.43
--- html_node/Non_002dGNU-Standards.html 12 Jan 2012 19:20:23 -0000
1.42
+++ html_node/Non_002dGNU-Standards.html 11 Mar 2012 00:26:50 -0000
1.43
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Non-GNU Standards</title>
@@ -114,9 +114,8 @@
<p>
Next: <a href="Semantics.html#Semantics" accesskey="n"
rel="next">Semantics</a>, Up: <a href="Program-Behavior.html#Program-Behavior"
accesskey="u" rel="up">Program Behavior</a> [<a
href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
-<p>
-</p>
+
</body>
</html>
Index: html_node/OID-Allocations.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/OID-Allocations.html,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -b -r1.26 -r1.27
--- html_node/OID-Allocations.html 12 Jan 2012 19:20:23 -0000 1.26
+++ html_node/OID-Allocations.html 11 Mar 2012 00:26:50 -0000 1.27
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: OID Allocations</title>
@@ -124,9 +124,8 @@
</pre></div>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Option-Table.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Option-Table.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Option-Table.html 12 Jan 2012 19:20:23 -0000 1.52
+++ html_node/Option-Table.html 11 Mar 2012 00:26:50 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Option Table</title>
@@ -1538,9 +1538,8 @@
<p>
Next: <a href="OID-Allocations.html#OID-Allocations" accesskey="n"
rel="next">OID Allocations</a>, Previous: <a
href="Dynamic-Plug_002dIn-Interfaces.html#Dynamic-Plug_002dIn-Interfaces"
accesskey="p" rel="previous">Dynamic Plug-In Interfaces</a>, Up: <a
href="Program-Behavior.html#Program-Behavior" accesskey="u" rel="up">Program
Behavior</a> [<a href="index.html#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Preface.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Preface.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Preface.html 12 Jan 2012 19:20:23 -0000 1.52
+++ html_node/Preface.html 11 Mar 2012 00:26:50 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Preface</title>
@@ -124,7 +124,7 @@
<a
href="http://www.gnu.org/software/hello/hello.html";>http://www.gnu.org/software/hello/hello.html</a>.
</p>
<p>This release of the GNU Coding Standards was last updated
-January 8, 2012.
+March 8, 2012.
</p>
<hr>
@@ -132,9 +132,8 @@
<p>
Next: <a href="Legal-Issues.html#Legal-Issues" accesskey="n" rel="next">Legal
Issues</a>, Previous: <a href="index.html#Top" accesskey="p"
rel="previous">Top</a>, Up: <a href="index.html#Top" accesskey="u"
rel="up">Top</a> [<a href="index.html#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Printed-Manuals.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Printed-Manuals.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Printed-Manuals.html 12 Jan 2012 19:20:24 -0000 1.52
+++ html_node/Printed-Manuals.html 11 Mar 2012 00:26:51 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Printed Manuals</title>
@@ -77,9 +77,8 @@
<p>It is also useful to explain in the on-line forms of the manual how the
user can print out the manual from the sources.
</p>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Program-Behavior.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Program-Behavior.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Program-Behavior.html 12 Jan 2012 19:20:24 -0000 1.52
+++ html_node/Program-Behavior.html 11 Mar 2012 00:26:51 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Program Behavior</title>
@@ -99,9 +99,8 @@
</td></tr>
</table>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Quote-Characters.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Quote-Characters.html,v
retrieving revision 1.44
retrieving revision 1.45
diff -u -b -r1.44 -r1.45
--- html_node/Quote-Characters.html 12 Jan 2012 19:20:24 -0000 1.44
+++ html_node/Quote-Characters.html 11 Mar 2012 00:26:51 -0000 1.45
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Quote Characters</title>
@@ -110,9 +110,8 @@
</p>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Reading-Non_002dFree-Code.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Reading-Non_002dFree-Code.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Reading-Non_002dFree-Code.html 12 Jan 2012 19:20:24 -0000
1.52
+++ html_node/Reading-Non_002dFree-Code.html 11 Mar 2012 00:26:51 -0000
1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Reading Non-Free Code</title>
@@ -105,9 +105,8 @@
<p>
Next: <a href="Contributions.html#Contributions" accesskey="n"
rel="next">Contributions</a>, Up: <a href="Legal-Issues.html#Legal-Issues"
accesskey="u" rel="up">Legal Issues</a> [<a
href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Reading-other-Manuals.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Reading-other-Manuals.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Reading-other-Manuals.html 12 Jan 2012 19:20:24 -0000
1.52
+++ html_node/Reading-other-Manuals.html 11 Mar 2012 00:26:51 -0000
1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Reading other Manuals</title>
@@ -79,9 +79,8 @@
documentation. Copying from free documentation may be ok; please check
with the FSF about the individual case.
</p>
-<p>
-</p>
+
</body>
</html>
Index: html_node/References.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/References.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/References.html 12 Jan 2012 19:20:25 -0000 1.52
+++ html_node/References.html 11 Mar 2012 00:26:51 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: References</title>
@@ -178,9 +178,8 @@
<p>
Next: <a
href="GNU-Free-Documentation-License.html#GNU-Free-Documentation-License"
accesskey="n" rel="next">GNU Free Documentation License</a>, Previous: <a
href="Managing-Releases.html#Managing-Releases" accesskey="p"
rel="previous">Managing Releases</a>, Up: <a href="index.html#Top"
accesskey="u" rel="up">Top</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
</div>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Releases.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Releases.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Releases.html 12 Jan 2012 19:20:26 -0000 1.52
+++ html_node/Releases.html 11 Mar 2012 00:26:52 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Releases</title>
@@ -152,9 +152,8 @@
<p>
Previous: <a href="Makefile-Conventions.html#Makefile-Conventions"
accesskey="p" rel="previous">Makefile Conventions</a>, Up: <a
href="Managing-Releases.html#Managing-Releases" accesskey="u" rel="up">Managing
Releases</a> [<a href="index.html#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Semantics.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Semantics.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Semantics.html 12 Jan 2012 19:20:27 -0000 1.52
+++ html_node/Semantics.html 11 Mar 2012 00:26:52 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Semantics</title>
@@ -183,9 +183,8 @@
<p>
Next: <a href="Libraries.html#Libraries" accesskey="n"
rel="next">Libraries</a>, Previous: <a
href="Non_002dGNU-Standards.html#Non_002dGNU-Standards" accesskey="p"
rel="previous">Non-GNU Standards</a>, Up: <a
href="Program-Behavior.html#Program-Behavior" accesskey="u" rel="up">Program
Behavior</a> [<a href="index.html#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Simple-Changes.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Simple-Changes.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Simple-Changes.html 12 Jan 2012 19:20:27 -0000 1.52
+++ html_node/Simple-Changes.html 11 Mar 2012 00:26:52 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Simple Changes</title>
@@ -97,9 +97,8 @@
project gets copyright assignments from its contributors, so as to
make the records of authorship more accurate.
</p>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Source-Language.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Source-Language.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Source-Language.html 12 Jan 2012 19:20:28 -0000 1.52
+++ html_node/Source-Language.html 11 Mar 2012 00:26:52 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Source Language</title>
@@ -118,9 +118,8 @@
<p>
Next: <a href="Compatibility.html#Compatibility" accesskey="n"
rel="next">Compatibility</a>, Up: <a href="Design-Advice.html#Design-Advice"
accesskey="u" rel="up">Design Advice</a> [<a
href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Standard-C.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Standard-C.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Standard-C.html 12 Jan 2012 19:20:29 -0000 1.52
+++ html_node/Standard-C.html 11 Mar 2012 00:26:52 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Standard C</title>
@@ -140,9 +140,8 @@
<p>
Next: <a href="Conditional-Compilation.html#Conditional-Compilation"
accesskey="n" rel="next">Conditional Compilation</a>, Previous: <a
href="Using-Extensions.html#Using-Extensions" accesskey="p"
rel="previous">Using Extensions</a>, Up: <a
href="Design-Advice.html#Design-Advice" accesskey="u" rel="up">Design
Advice</a> [<a href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Standard-Targets.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Standard-Targets.html,v
retrieving revision 1.54
retrieving revision 1.55
diff -u -b -r1.54 -r1.55
--- html_node/Standard-Targets.html 12 Jan 2012 19:20:30 -0000 1.54
+++ html_node/Standard-Targets.html 11 Mar 2012 00:26:52 -0000 1.55
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Standard Targets</title>
@@ -413,9 +413,8 @@
<p>
Next: <a href="Install-Command-Categories.html#Install-Command-Categories"
accesskey="n" rel="next">Install Command Categories</a>, Previous: <a
href="Directory-Variables.html#Directory-Variables" accesskey="p"
rel="previous">Directory Variables</a>, Up: <a
href="Makefile-Conventions.html#Makefile-Conventions" accesskey="u"
rel="up">Makefile Conventions</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
</div>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Style-of-Change-Logs.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Style-of-Change-Logs.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Style-of-Change-Logs.html 12 Jan 2012 19:20:31 -0000 1.52
+++ html_node/Style-of-Change-Logs.html 11 Mar 2012 00:26:53 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Style of Change Logs</title>
@@ -140,9 +140,8 @@
<p>
Next: <a href="Simple-Changes.html#Simple-Changes" accesskey="n"
rel="next">Simple Changes</a>, Previous: <a
href="Change-Log-Concepts.html#Change-Log-Concepts" accesskey="p"
rel="previous">Change Log Concepts</a>, Up: <a
href="Change-Logs.html#Change-Logs" accesskey="u" rel="up">Change Logs</a>
[<a href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Syntactic-Conventions.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Syntactic-Conventions.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Syntactic-Conventions.html 12 Jan 2012 19:20:32 -0000
1.52
+++ html_node/Syntactic-Conventions.html 11 Mar 2012 00:26:53 -0000
1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Syntactic Conventions</title>
@@ -90,10 +90,10 @@
as <code>lint</code>, <code>clang</code>, and GCC with extra warnings
options such as ‘<samp>-Wconversion</samp>’ and
‘<samp>-Wundef</samp>’. These
tools can help find bugs and unclear code, but they can also generate
-so many false alarms that that it hurts readability to silence them
-with unnecessary casts, wrappers, and other complications. For
-example, please don’t insert casts to <code>void</code> or calls to
-do-nothing functions merely to pacify a lint checker.
+so many false alarms that it hurts readability to silence them with
+unnecessary casts, wrappers, and other complications. For example,
+please don’t insert casts to <code>void</code> or calls to do-nothing
+functions merely to pacify a lint checker.
</p>
<p>Declarations of external functions and functions to appear later in the
source file should all go in one place near the beginning of the file
@@ -217,9 +217,8 @@
<p>
Next: <a href="Names.html#Names" accesskey="n" rel="next">Names</a>, Previous:
<a href="Comments.html#Comments" accesskey="p" rel="previous">Comments</a>, Up:
<a href="Writing-C.html#Writing-C" accesskey="u" rel="up">Writing C</a>
[<a href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
-<p>
-</p>
+
</body>
</html>
Index: html_node/System-Functions.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/System-Functions.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/System-Functions.html 12 Jan 2012 19:20:33 -0000 1.52
+++ html_node/System-Functions.html 11 Mar 2012 00:26:53 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: System Functions</title>
@@ -142,9 +142,8 @@
<p>
Next: <a href="Internationalization.html#Internationalization" accesskey="n"
rel="next">Internationalization</a>, Previous: <a
href="CPU-Portability.html#CPU-Portability" accesskey="p" rel="previous">CPU
Portability</a>, Up: <a href="Writing-C.html#Writing-C" accesskey="u"
rel="up">Writing C</a> [<a href="index.html#SEC_Contents" title="Table
of contents" rel="contents">Contents</a>][<a href="Index.html#Index"
title="Index" rel="index">Index</a>]</p>
</div>
-<p>
-</p>
+
</body>
</html>
Index: html_node/System-Portability.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/System-Portability.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/System-Portability.html 12 Jan 2012 19:20:33 -0000 1.52
+++ html_node/System-Portability.html 11 Mar 2012 00:26:53 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: System Portability</title>
@@ -128,9 +128,8 @@
<p>
Next: <a href="CPU-Portability.html#CPU-Portability" accesskey="n"
rel="next">CPU Portability</a>, Previous: <a href="Names.html#Names"
accesskey="p" rel="previous">Names</a>, Up: <a href="Writing-C.html#Writing-C"
accesskey="u" rel="up">Writing C</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
</div>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Trademarks.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Trademarks.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Trademarks.html 12 Jan 2012 19:20:34 -0000 1.52
+++ html_node/Trademarks.html 11 Mar 2012 00:26:53 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Trademarks</title>
@@ -95,9 +95,8 @@
symbol names), we abbreviate it to “w”. For instance, the files
and
functions in Emacs that deal with Windows start with
‘<samp>w32</samp>’.
</p>
-<p>
-</p>
+
</body>
</html>
Index: html_node/User-Interfaces.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/User-Interfaces.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/User-Interfaces.html 12 Jan 2012 19:20:34 -0000 1.52
+++ html_node/User-Interfaces.html 11 Mar 2012 00:26:54 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: User Interfaces</title>
@@ -104,9 +104,8 @@
<p>
Next: <a href="Graphical-Interfaces.html#Graphical-Interfaces" accesskey="n"
rel="next">Graphical Interfaces</a>, Previous: <a href="Errors.html#Errors"
accesskey="p" rel="previous">Errors</a>, Up: <a
href="Program-Behavior.html#Program-Behavior" accesskey="u" rel="up">Program
Behavior</a> [<a href="index.html#SEC_Contents" title="Table of
contents" rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Using-Extensions.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Using-Extensions.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Using-Extensions.html 12 Jan 2012 19:20:34 -0000 1.52
+++ html_node/Using-Extensions.html 11 Mar 2012 00:26:54 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Using Extensions</title>
@@ -96,9 +96,8 @@
compiler, then no one can compile them without having them installed
already. That would be extremely troublesome in certain cases.
</p>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Utilities-in-Makefiles.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Utilities-in-Makefiles.html,v
retrieving revision 1.54
retrieving revision 1.55
diff -u -b -r1.54 -r1.55
--- html_node/Utilities-in-Makefiles.html 12 Jan 2012 19:20:34 -0000
1.54
+++ html_node/Utilities-in-Makefiles.html 11 Mar 2012 00:26:54 -0000
1.55
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Utilities in Makefiles</title>
@@ -138,9 +138,8 @@
<p>
Next: <a href="Command-Variables.html#Command-Variables" accesskey="n"
rel="next">Command Variables</a>, Previous: <a
href="Makefile-Basics.html#Makefile-Basics" accesskey="p"
rel="previous">Makefile Basics</a>, Up: <a
href="Makefile-Conventions.html#Makefile-Conventions" accesskey="u"
rel="up">Makefile Conventions</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
</div>
-<p>
-</p>
+
</body>
</html>
Index: html_node/Writing-C.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/Writing-C.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/Writing-C.html 12 Jan 2012 19:20:34 -0000 1.52
+++ html_node/Writing-C.html 11 Mar 2012 00:26:54 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Writing C</title>
@@ -95,9 +95,8 @@
</td></tr>
</table>
-<p>
-</p>
+
</body>
</html>
Index: html_node/_002d_002dhelp.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/_002d_002dhelp.html,v
retrieving revision 1.36
retrieving revision 1.37
diff -u -b -r1.36 -r1.37
--- html_node/_002d_002dhelp.html 12 Jan 2012 19:20:34 -0000 1.36
+++ html_node/_002d_002dhelp.html 11 Mar 2012 00:26:54 -0000 1.37
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: --help</title>
@@ -90,9 +90,8 @@
<p>It is ok to mention other appropriate mailing lists and web pages.
</p>
-<p>
-</p>
+
</body>
</html>
Index: html_node/_002d_002dversion.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/_002d_002dversion.html,v
retrieving revision 1.37
retrieving revision 1.38
diff -u -b -r1.37 -r1.38
--- html_node/_002d_002dversion.html 12 Jan 2012 19:20:34 -0000 1.37
+++ html_node/_002d_002dversion.html 11 Mar 2012 00:26:54 -0000 1.38
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: --version</title>
@@ -117,7 +117,7 @@
each on a separate line.
</p>
<p>Next should follow a line stating the license, preferably using one of
-abbrevations below, and a brief statement that the program is free
+abbreviations below, and a brief statement that the program is free
software, and that users are free to copy and change it. Also mention
that there is no warranty, to the extent permitted by law. See
recommended wording below.
@@ -241,9 +241,8 @@
<p>
Next: <a href="_002d_002dhelp.html#g_t_002d_002dhelp" accesskey="n"
rel="next">--help</a>, Up: <a
href="Command_002dLine-Interfaces.html#Command_002dLine-Interfaces"
accesskey="u" rel="up">Command-Line Interfaces</a> [<a
href="index.html#SEC_Contents" title="Table of contents"
rel="contents">Contents</a>][<a href="Index.html#Index" title="Index"
rel="index">Index</a>]</p>
</div>
-<p>
-</p>
+
</body>
</html>
Index: html_node/index.html
===================================================================
RCS file: /web/www/www/prep/standards/html_node/index.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- html_node/index.html 12 Jan 2012 19:20:34 -0000 1.52
+++ html_node/index.html 11 Mar 2012 00:26:54 -0000 1.53
@@ -1,6 +1,6 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<html>
-<!-- The GNU coding standards, last updated January 8, 2012.
+<!-- The GNU coding standards, last updated March 8, 2012.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -12,7 +12,7 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by Texinfo 0.01, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by Texinfo 4.13.90+dev, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Coding Standards: Top</title>
@@ -25,7 +25,7 @@
<link href="#Top" rel="start" title="Top">
<link href="Index.html#Index" rel="index" title="Index">
<link href="#SEC_Contents" rel="contents" title="Table of Contents">
-<link href="../dir/index.html#Top" rel="up" title="(dir)">
+<link href="../dir/index.html" rel="up" title="(dir)">
<link href="Preface.html#Preface" rel="next" title="Preface">
<style type="text/css">
<!--
@@ -164,13 +164,13 @@
<a name="Top"></a>
<div class="header">
<p>
-Next: <a href="Preface.html#Preface" accesskey="n" rel="next">Preface</a>, Up:
<a href="../dir/index.html#Top" accesskey="u" rel="up">(dir)</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="Preface.html#Preface" accesskey="n" rel="next">Preface</a>, Up:
<a href="../dir/index.html" accesskey="u" rel="up">(dir)</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
</div>
<hr>
<a name="GNU-Coding-Standards"></a>
<h1 class="top">GNU Coding Standards</h1>
-<p>The GNU coding standards, last updated January 8, 2012.
+<p>The GNU coding standards, last updated March 8, 2012.
</p>
<p>Copyright © 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
@@ -211,11 +211,10 @@
<hr>
<div class="header">
<p>
-Next: <a href="Preface.html#Preface" accesskey="n" rel="next">Preface</a>, Up:
<a href="../dir/index.html#Top" accesskey="u" rel="up">(dir)</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
+Next: <a href="Preface.html#Preface" accesskey="n" rel="next">Preface</a>, Up:
<a href="../dir/index.html" accesskey="u" rel="up">(dir)</a> [<a
href="#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
</div>
-<p>
-</p>
+
</body>
</html>
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- www/prep/standards index.html standards.dvi.gz ...,
Karl Berry <=