Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site pedsgd.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!mtuxo!mtunh!mtung!mtunf!ariel!vax135!petsd!pedsgd!bob
From: bob@pedsgd.UUCP (Robert A. Weiler)
Newsgroups: net.lang.c
Subject: Re: more about programming style
Message-ID: <218@pedsgd.UUCP>
Date: Thu, 25-Jul-85 12:16:30 EDT
Article-I.D.: pedsgd.218
Posted: Thu Jul 25 12:16:30 1985
Date-Received: Sat, 27-Jul-85 00:02:59 EDT
References: <11457@brl-tgr.ARPA> <68@ucbcad.UUCP> <1693@reed.UUCP> <441@myriasb.UUCP>
Reply-To: bob@pedsgd.UUCP (Robert A. Weiler)
Organization: Perkin-Elmer, Tinton Falls, NJ
Lines: 26
Summary: 

Organization : Perkin-Elmer DSG, Tinton Falls NJ
Keywords: 

Ill try to keep this short. This has gone on long enough. People use ++ and
other funny assignments because they are part of C and occur all over
the place in existing C code and C programming books. It should take
the average individual 5-15 minutes to figure out what these do, and then
he/she/it should remember it for life. This is a non-issue. A real problem
in C is type declaration syntax, as should be obvious from the number of
requests Chris Torek apparently got for cdecl source ( thanks Chris ).
I find a partial solution to the def problem is to use the following
style of declarations religously.

#define MYSTRUCT_T	struct mystruct
struct mystruct {
	int		whatever;
	MYSTRUCT_T	*next;
};
typedef MYSTRUCT_T	mystruct_t, *mystruct_p;
#define	MYSTRUCTSZ	(sizeof(mystruct_t))
#define	NULLMYSTRUCT	((mystruct_p)0)

I would appreciate comments, suggestions, etc. on additional ways to
make type declarations more readable. But enough already about ++.

Bob Weiler.