Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: notesfiles
Path: utzoo!watmath!clyde!burl!ulysses!harpo!seismo!hao!hplabs!hp-pcd!hpfcla!ajs
From: ajs@hpfcla.UUCP
Newsgroups: net.lang.c
Subject: Re: return expr and Decus-C
Message-ID: <40100004@hpfcla.UUCP>
Date: Tue, 15-May-84 19:59:00 EDT
Article-I.D.: hpfcla.40100004
Posted: Tue May 15 19:59:00 1984
Date-Received: Mon, 21-May-84 06:22:59 EDT
References: <478@decvax.UUCP>
Organization: Hewlett-Packard Fort Collins Systems Division - Fort Collins, CO
Lines: 40
Nf-ID: #R:decvax:-47800:hpfcla:40100004:000:1273
Nf-From: hpfcla!ajs    May 10 15:59:00 1984

> return expr;
> is preferable to
> return(expr);
> since the latter looks like a function call (which it is not).

Unless, of course, expr is more complicated than the null string, in which
case parentheses are a very nice way to set it apart.  But seriously...


	RETURN(3)		Parody Systems			RETURN(3)


	NAME
	   return -- return from C procedure call

	SYNOPSIS
	   void return (value)
	   anytype value;

	DESCRIPTION
	   This  procedure  never  returns to the  caller.  Instead,  it
	   casts the given  value to the  procedure  type of the calling
	   procedure,  without loss of size or accuracy.  Then it causes
	   the user  program  to  continue  immediately  after the place
	   where the calling  procedure was itself  called.  The calling
	   procedure  appears  to  return  value  to  its  caller  as  a
	   constant of the proper type, should the caller care to use it
	   in an expression (including a simple assignment).

	   The value parameter is optional and may be omitted.

	   If a  procedure  ends  without  calling  return()  first, the
	   operating system calls it for you with no parameters.

	SEE ALSO
	   setjmp(3)

	BUGS
	   Due to a bug in the compiler,  this  procedure  can be called
	   without placing parentheses around its parameter.