Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!nuchat!sugar!peter
From: peter@sugar.UUCP (Peter da Silva)
Newsgroups: comp.lang.c
Subject: Re: documentation standards........
Message-ID: <913@sugar.UUCP>
Date: Mon, 26-Oct-87 07:39:34 EST
Article-I.D.: sugar.913
Posted: Mon Oct 26 07:39:34 1987
Date-Received: Wed, 28-Oct-87 06:11:16 EST
References: <9897@brl-adm.ARPA>
Organization: Sugar Land UNIX - Houston, TX
Lines: 58
Summary: Indenting style.

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.

I know I can always run it through "cb", but that tends to mess up the comments
something fierce.

Now whether you do this:

	if(...) {

or this:

	if(...)
	{

or this:

	if(...)
		{

is really irrelevant. It would be nice if you can indent the body of your
functions, though:

foo()
{
	int variable;

	code;

	if(...)
	{
		code;
	}
}

is a bit easier to work with than:

foo()
{
int variable;

code;

if(...)
	{
	code;
	}
}

it may take up a bit more room, but that's what the variable tabs are for.
I always have trouble remembering whether I'm in a function or not.
-- 
-- Peter da Silva  `-_-'  ...!hoptoad!academ!uhnix1!sugar!peter
-- Disclaimer: These U aren't mere opinions... these are *values*.