Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!yetti!geac!daveb
From: daveb@geac.UUCP
Newsgroups: comp.lang.c
Subject: Re: documentation standards........
Message-ID: <1735@geac.UUCP>
Date: Thu, 29-Oct-87 08:45:53 EST
Article-I.D.: geac.1735
Posted: Thu Oct 29 08:45:53 1987
Date-Received: Fri, 30-Oct-87 23:53:39 EST
References: <9897@brl-adm.ARPA> <913@sugar.UUCP>
Reply-To: daveb@geac.UUCP (Dave Collier-Brown)
Organization: The little blue rock next to that twinkly star.
Lines: 24

In article <913@sugar.UUCP> peter@sugar.UUCP (Peter da Silva) writes:
>Indents should be one tab-stop. That way you can set your editor and your
>"make print" command line to set the indentation depth your way, and some
>other person who might be using your code can set them his, her, or its way.
>
>I myself like changing the tab-size in my editor depending on how heavily
>indented the code I'm working on is.

  Back in the Multics days, a tab was 10 characters, or 1" on the
standard (printing) terminal then in use.
  This had the pleasant effect of discouraging deeply-indented
nested blocks of code, which in turn tended to discourage long
procedures/functions.

  As a result, I always recommend "broad" tabs for C and Ada (which
can be easily written with a "comb-like" indenting style), and
"narrow" tabs only for Pascal and sh.

 --dave
-- 
 David Collier-Brown.                 {mnetor|yetti|utgpu}!geac!daveb
 Geac Computers International Inc.,   |  Computer Science loses its
 350 Steelcase Road,Markham, Ontario, |  memory (if not its mind)
 CANADA, L3R 1B3 (416) 475-0525 x3279 |  every 6 months.