Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site danews.UUCP
Path: utzoo!decvax!bellcore!ulysses!burl!clyde!cbosgd!danews!lvc
From: lvc@danews.UUCP (Larry Cipriani)
Newsgroups: net.lang.c
Subject: What's wrong with printf( ) , return ?
Message-ID: <123@danews.UUCP>
Date: Mon, 19-May-86 08:20:17 EDT
Article-I.D.: danews.123
Posted: Mon May 19 08:20:17 1986
Date-Received: Tue, 20-May-86 01:18:47 EDT
Distribution: na
Organization: AT&T Bell Labs, Columbus OH
Lines: 24

> > 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 ?

> return isn't an expression.  You can't write

> 	printf("usage: foo bar\n") , if (!fflag) exit(1);

> either.

I knew that return wasn't an expression.  The fact that you can
do `control flow' with , seperating expressions makes me wonder
why this wasn't extended to include 'some' statements such as return.

Thanks,

-- 

Larry Cipriani		AT&T Network Systems
cbsck!lvc	Mail responses to ihnp4!cbsck!lvc please - thanks