Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site pucc-k
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!ihnp4!inuxc!pur-ee!CS-Mordred!Pucc-H:Pucc-I:Pucc-K:agt
From: agt@pucc-k (Kevin Braunsdorf)
Newsgroups: net.lang.c
Subject: Inconsistency in Style -> Unreadable Code
Message-ID: <1207@pucc-k>
Date: Fri, 26-Jul-85 17:26:56 EDT
Article-I.D.: pucc-k.1207
Posted: Fri Jul 26 17:26:56 1985
Date-Received: Mon, 29-Jul-85 06:10:11 EDT
References: work at PUCC
Organization: Solon Aquilla's Magic & Art Gallery
Lines: 35


    All: I am a Computing Center Consultant at Purdue so I see more
different styles of coding per week than most programmers do in a year:
in my view the only bad style is an inconsistent one, eg:

	kp = ++i * j;
	j += 1;

	should be any of:
	i++;			i += 1;		kp = ++i * j++;
	kp = i * j;		kp = i * j;
	j++;			j += 1;

	or even:
	kp = (i += 1) * j;
	j += 1;

    Anything that I can notice a set pattern to will help me read the code:
as to the formatting of the code, I personally use
	while (exp) {
	    ...
	}	/* line close curly with while	*/
    but
	while (exp) {
	    ...
	    }	/* indent curly too		*/
    works for me too, as long as
	fnx()
	    {
	    ...
	    }
    is used too!

						:wq
						Kevin Braunsdorf