From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,791530e499e6a7f9 X-Google-Attributes: gid103376,public From: tmoran@bix.com Subject: Re: ada writing guide Date: 2000/04/15 Message-ID: #1/1 X-Deja-AN: 611406404 References: <8d82lq$4fp$1@hobbes2.crc.com> X-Complaints-To: abuse@pacbell.net X-Trace: news.pacbell.net 955775888 206.170.2.108 (Fri, 14 Apr 2000 22:18:08 PDT) Organization: SBC Internet Services NNTP-Posting-Date: Fri, 14 Apr 2000 22:18:08 PDT Newsgroups: comp.lang.ada Date: 2000-04-15T00:00:00+00:00 List-Id: > http://www.delorie.com/gnu/docs/GNU/standards_toc.html > > This provides a coding stabndard for C, which could be considered "strict." It's hard to know what to say. A document dated 1999 that gives a standard for C and cautions against using any other language, including C++. A document whose "C style" part is all of 550 lines, or ten pages, in length, whereas "Ada Quality and Style" manages somehow to take 270 pages. A "strict" standard for the "C" language with statements like: "Please use formfeed characters (control-L) to divide the program into pages" "Insert extra parentheses so that Emacs will indent the code properly." "We find it easier to read a program when it has spaces before the operator, not after one. Here is the right way:" "Please put two spaces after the end of a sentence in your comments, so that the Emacs sentence commands will work." "Please write the comments in a GNU program in English, because English is the one language that nearly all programmers in all countries can read." I guess the adjective "strict" does apply in cases like: "It is important to put the open-brace that starts the body of a C function in column zero, and avoid putting any other open-brace or open-parenthesis or open-bracket in column zero. Several tools look for open-braces in column zero to find the beginnings of C functions. These tools will not work on code not formatted that way. It is also important for function definitions to start the name of the function in column zero. This helps people to search for function definitions, and may also help certain tools recognize them." I prefer Ada, and even if I was coding in GNU C, I'd read Ada Quality and Style for ideas.