Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!mit-eddie!bbn.com!papaya.bbn.com!rsalz
From: rsalz@bbn.com (Rich Salz)
Newsgroups: comp.lang.c
Subject: Re: Coding Standards.  was: a style question
Message-ID: <3072@litchi.bbn.com>
Date: 5 Dec 90 22:38:23 GMT
References: <L237B.5@xds13.ferranti.com>
Organization: BBN Systems and Technology, Inc.
Lines: 22

In <L237B.5@xds13.ferranti.com> peter@ficc.ferranti.com (Peter da Silva) writes:
>My objection to beautifiers is what they do to stuff like this:
	ARGDESC	Args[] =
	{
		'T',	ARGOPT,		argChar,	__ &TabChar,	"Tab",
		'a',	ARGOPT,		argBool,	__ &AllFlag,	"All",
		'1',	ARGOPT,		argBool,	__ &OneFlag,	"First",
		' ',	ARGREQ,		argStr,		__ &Format,	"Format",
		' ',	ARGREQ|ARGLIST,	listStr,	__ &CmdNames,	"Command",
		'f',	ARGOPT|ARGLIST,	listStr,	__ &Files,	"File",
		ENDOFARGS
	};
If you put the curly braces in then there would be no problem:
	{ 'T',    ARGOPT,         argChar,        __ &TabChar,    "Tab", }
Anyone who maintains the code after you will thank you for it.

The other problem is to not use the C pre-processor to change the syntax of
the language, as __ and ENDOFARGS apparently do.
	/r$
-- 
Please send comp.sources.unix-related mail to rsalz@uunet.uu.net.
Use a domain-based address or give alternate paths, or you may lose out.