Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site ulysses.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!ggs
From: ggs@ulysses.UUCP (Griff Smith)
Newsgroups: net.lang.c
Subject: Re:  questions from using lint
Message-ID: <1247@ulysses.UUCP>
Date: Sun, 4-May-86 11:29:56 EDT
Article-I.D.: ulysses.1247
Posted: Sun May  4 11:29:56 1986
Date-Received: Tue, 6-May-86 04:11:58 EDT
References: <501@brl-smoke.ARPA>
Organization: AT&T Bell Laboratories, Murray Hill
Lines: 37

> 	Most People			Your's Truly
> 
> 	if (c) {			if (c)
> 		w = y;				w = x,
> 		y = z;				y = z;
> 	}				/* look ma, no brace */
...
> Sufficeth to say that I use a lot of commas in my code. Unfortunately,
> I cannot do this if either statement is a control struxure, *except* return.
> 
> 	Most People			Your's Truly
> 
> 	if (c) {			if (c)
> 		w = y;				return w = x,
> 		return;
> 	}				/* look ma, no brace */
> 
> When I want to return a *real* value, I use `return(exp)' using *explicit*
> parens. I only do this in void funxions of course. I cannot see *any*
> implementation doing either of the following:
> 
> 	1) barfing because I returned an *extra* value sometimes
> 	2) barfing because I added an extra argument
> 
> Now you may claim that this is `bad programming practice', but I claim
> that it is just a convention, ...
...
> 	(Root Boy) Jim Cottrell		<rbj@cmr>

"Thank you, Mr Cottrell.  It is refreshing when job applicants are so candid
during an interview; we will notify you of our decision in a few weeks..."
-- 

Griff Smith	AT&T (Bell Laboratories), Murray Hill
Phone:		(201) 582-7736
Internet:	ggs@ulysses.uucp
UUCP:		ulysses!ggs  ( {allegra|ihnp4}!ulysses!ggs )