Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site ucbvax.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!cbosgd!ucbvax!info-vax
From: info-vax@ucbvax.ARPA
Newsgroups: fa.info-vax
Subject: Re: Possible VAX/VMS PL/I Bug
Message-ID: <4763@ucbvax.ARPA>
Date: Tue, 12-Feb-85 16:26:54 EST
Article-I.D.: ucbvax.4763
Posted: Tue Feb 12 16:26:54 1985
Date-Received: Wed, 13-Feb-85 04:35:36 EST
Sender: daemon@ucbvax.ARPA
Organization: University of California at Berkeley
Lines: 15

From: lionel%speedy.DEC@decwrl.ARPA  (Steve Lionel)

Regarding Jerry Bakin's question about VAX PL/I warnings:

VAX PL/I keeps track (at run time) what entry point a procedure was entered by.
If the procedure has entry points with different return datatypes, for each
RETURN statement it generates several alternative code sequences to convert the
specified return value to all the possible datatypes.  At run time, it jumps to
the one related to the ENTRY point that was used. 

Since a conversion is "possible", VAX PL/I generates a warning message.  Thus
the program "compiles" under both Multics and VAX PL/I.  It's just that
the VAX compiler happens to give a warning message for such "potential"
datatype conversions (in fact it gives a warning for ALL implicit conversions).
It can be overidden with the /NOWARN switch.