[ < ] [ > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

Index

Jump to:   #   -  
A   B   C   D   E   F   G   I   L   M   N   O   P   R   S   T   W  

Index Entry Section

#
#endif, commenting5.2 Commenting Your Work

-
`--help' option4.6 Standards for Command Line Interfaces
`--version' option4.6 Standards for Command Line Interfaces
`-Wall' compiler option5.3 Clean Use of C Constructs

A
accepting contributions2.2 Accepting Contributions
address for bug reports4.6 Standards for Command Line Interfaces
ANSI C standard3.4 Standard C and Pre-Standard C
arbitrary limits on data4.1 Writing Robust Programs
autoconf5.5 Portability between System Types
avoiding proprietary code2.1 Referring to Proprietary Programs

B
behavior, dependent on program's name4.4 Standards for Interfaces Generally
binary packages7.2.6 Install Command Categories
bindir7.2.4 Variables for Installation Directories
braces, in C source5.1 Formatting Your Source Code
bug reports4.6 Standards for Command Line Interfaces

C
canonical name of a program4.6 Standards for Command Line Interfaces
casting pointers to integers5.6 Portability between CPUs
change logs6.8 Change Logs
change logs, conditional changes6.8.4 Conditional Changes
change logs, style6.8.2 Style of Change Logs
command-line arguments, decoding4.1 Writing Robust Programs
command-line interface4.6 Standards for Command Line Interfaces
commenting5.2 Commenting Your Work
compatibility with C and POSIX standards3.2 Compatibility with Other Implementations
compiler warnings5.3 Clean Use of C Constructs
conditional changes, and change logs6.8.4 Conditional Changes
conditionals, comments for5.2 Commenting Your Work
configure7.1 How Configuration Should Work
control-L5.1 Formatting Your Source Code
conventions for makefiles7.2 Makefile Conventions
corba4.5 Standards for Graphical Interfaces
credits for manuals6.5 Manual Credits

D
data types, and portability5.6 Portability between CPUs
declaration for system functions5.7 Calling System Functions
documentation6. Documenting Programs
doschk5.4 Naming Variables and Functions
downloading this manual1. About the GNU Coding Standards

E
error messages4.1 Writing Robust Programs
error messages, formatting4.3 Formatting Error Messages
exec_prefix7.2.4 Variables for Installation Directories
expressions, splitting5.1 Formatting Your Source Code

F
file usage4.9 File Usage
file-name limitations5.4 Naming Variables and Functions
formatting error messages4.3 Formatting Error Messages
formatting source code5.1 Formatting Your Source Code
formfeed5.1 Formatting Your Source Code
function argument, declaring5.3 Clean Use of C Constructs
function prototypes3.4 Standard C and Pre-Standard C

G
getopt4.6 Standards for Command Line Interfaces
gettext5.8 Internationalization
gnome4.5 Standards for Graphical Interfaces
graphical user interface4.5 Standards for Graphical Interfaces
gtk4.5 Standards for Graphical Interfaces
GUILE3.1 Which Languages to Use

I
implicit int5.3 Clean Use of C Constructs
impossible conditions4.1 Writing Robust Programs
internationalization5.8 Internationalization

L
legal aspects2. Keeping Free Software Free
legal papers2.2 Accepting Contributions
libexecdir7.2.4 Variables for Installation Directories
libraries4.2 Library Behavior
library functions, and portability5.7 Calling System Functions
license for manuals6.4 License for Manuals
lint5.3 Clean Use of C Constructs
long option names4.7 Table of Long Options
long-named options4.6 Standards for Command Line Interfaces

M
makefile, conventions for7.2 Makefile Conventions
malloc return value4.1 Writing Robust Programs
man pages6.9 Man Pages
manual structure6.3 Manual Structure Details
memory allocation failure4.1 Writing Robust Programs
memory usage4.8 Memory Usage
message text, and internationalization5.8 Internationalization
mmap5.9 Mmap
multiple variables in a line5.3 Clean Use of C Constructs

N
names of variables and functions5.4 Naming Variables and Functions
`NEWS' file6.7 The NEWS File
non-POSIX systems, and portability5.5 Portability between System Types
non-standard extensions3.3 Using Non-standard Features
NUL characters4.1 Writing Robust Programs

O
open brace5.1 Formatting Your Source Code
optional features, configure-time7.1 How Configuration Should Work
options for compatibility3.2 Compatibility with Other Implementations
output device and program's behavior4.4 Standards for Interfaces Generally

P
packaging7.3 Making Releases
portability, and data types5.6 Portability between CPUs
portability, and library functions5.7 Calling System Functions
portability, between system types5.5 Portability between System Types
POSIX compatibility3.2 Compatibility with Other Implementations
POSIXLY_CORRECT, environment variable3.2 Compatibility with Other Implementations
post-installation commands7.2.6 Install Command Categories
pre-installation commands7.2.6 Install Command Categories
prefix7.2.4 Variables for Installation Directories
program configuration7.1 How Configuration Should Work
program design3. General Program Design
program name and its behavior4.4 Standards for Interfaces Generally
program's canonical name4.6 Standards for Command Line Interfaces
programming languges3.1 Which Languages to Use
proprietary programs2.1 Referring to Proprietary Programs

R
`README' file7.3 Making Releases
references to non-free material8. References to Non-Free Software and Documentation
releasing7. The Release Process

Jump to:   #   -  
A   B   C   D   E   F   G   I   L   M   N   O   P   R   S   T   W  

[ << ] [ >> ]           [Top] [Contents] [Index] [ ? ]

This document was generated by XEmacs Webmaster on August, 3 2012 using texi2html