Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!cmcl2!harvard!caip!princeton!allegra!ulysses!burl!clyde!cbosgd!danews!lvc
From: lvc@danews.UUCP (Larry Cipriani)
Newsgroups: net.lang.c
Subject: Re: What's wrong with printf() , exit() ? (oops)
Message-ID: <118@danews.UUCP>
Date: Sun, 11-May-86 13:49:33 EDT
Article-I.D.: danews.118
Posted: Sun May 11 13:49:33 1986
Date-Received: Mon, 19-May-86 01:54:32 EDT
References: <501@brl-smoke.ARPA> <797@bentley.UUCP> <117@danews.UUCP>
Organization: AT&T Bell Labs, Columbus OH
Lines: 21

I wrote:
>> What's wrong with
>> 	printf("usage: foo bar\n"), exit(1);
>> as above?
>> 

>Aside from style, exit is a statement syntatically but , requires
>expressions.  The compilers I've used will accept this and do
>what you'd expect.  Why is that ?  Is this a special exeption ?

Oops.  I mistakenly believed exit and return were both reserved words
in C but only return is.  There may be compilers that won't accept it
but they would be wrong.

	printf("usage: foo bar\n") , return 1 ;

seems reasonably "within C's style".  Comments ?
-- 

Larry Cipriani		Nothing is worse than having
danews!lvc		an itch you can never scratch