diff options
| author | Karl Berry <karl@freefriends.org> | 2006-12-01 19:34:34 +0000 |
|---|---|---|
| committer | Karl Berry <karl@freefriends.org> | 2006-12-01 19:34:34 +0000 |
| commit | 22be6a723b0822174c0748bf910217efd0700307 (patch) | |
| tree | 4d2653d0195a116172f7012f990fb4cb4d9a5f82 /doc | |
| parent | 9fefaeaf9b1eab89331cb1e1945b494a8c68a7af (diff) | |
| download | gnulib-22be6a723b0822174c0748bf910217efd0700307.tar.gz | |
autoupdate
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/standards.texi | 14 |
1 files changed, 9 insertions, 5 deletions
diff --git a/doc/standards.texi b/doc/standards.texi index 558746d80c..4403e143f5 100644 --- a/doc/standards.texi +++ b/doc/standards.texi @@ -3,7 +3,7 @@ @setfilename standards.info @settitle GNU Coding Standards @c This date is automagically updated when you save this file: -@set lastupdate November 15, 2006 +@set lastupdate November 30, 2006 @c %**end of header @dircategory GNU organization @@ -2201,10 +2201,14 @@ when writing GNU software. @cindex open brace @cindex braces, in C source It is important to put the open-brace that starts the body of a C -function in column one, and avoid putting any other open-brace or -open-parenthesis or open-bracket in column one. Several tools look -for open-braces in column one to find the beginnings of C functions. -These tools will not work on code not formatted that way. +function in column one, so that they will start a defun. Several +tools look for open-braces in column one to find the beginnings of C +functions. These tools will not work on code not formatted that way. + +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 @code{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 the function in column one. This helps people to search for function |