Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site elsie.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxl!ihnp4!zehntel!hplabs!hao!seismo!umcp-cs!cvl!elsie!ado
From: ado@elsie.UUCP
Newsgroups: net.lang.c
Subject: Re: Non-reentrant code generated by C compiler
Message-ID: <1182@elsie.UUCP>
Date: Thu, 23-Aug-84 11:20:27 EDT
Article-I.D.: elsie.1182
Posted: Thu Aug 23 11:20:27 1984
Date-Received: Sat, 25-Aug-84 07:08:26 EDT
References: <510@calgary.UUCP>, <1154@elsie.UUCP>, <4167@brl-tgr.ARPA>
Organization: NIH-LEC, Bethesda, MD
Lines: 13

> How about changing the lint message from "nonportable return of structure"
> to "structure return is nonreentrant".  There is nothing nonportable about
> struct-valued functions.

Actually, with all the muttering in this group of late on how to redo struct-
valued returns, returning a structure probably IS nonportable--sometimes it
will be reentrant, sometimes not.

And, of course, return of structures was absent before the advent of Version 7--
so struct-valued functions are not portable to Version 6 and its clones.
--
	...decvax!seismo!umcp-cs!elsie!ado	(301) 496-5688
	(DEC, VAX and Elsie are Digital Equipment Corp. and Borden's trademarks)