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!cbosgd!ucbvax!info-vax
From: info-vax@ucbvax.ARPA
Newsgroups: fa.info-vax
Subject: re: Possible VAX/VMS PL/I bug
Message-ID: <4840@ucbvax.ARPA>
Date: Thu, 14-Feb-85 20:14:39 EST
Article-I.D.: ucbvax.4840
Posted: Thu Feb 14 20:14:39 1985
Date-Received: Fri, 15-Feb-85 06:10:34 EST
Sender: daemon@ucbvax.ARPA
Organization: University of California at Berkeley
Lines: 19

From: Provan@LLL-MFE.ARPA


I don't know a thing about PL/I, but I'd say that this warning produced
by the VMS PL/I compiler is just the closest it can come to saying
"Kludgy code detected in routine".  Come on.  You expect the compiler
to sit by and watch you write a routine that has two different entry
points, each with different types of results, and not complain?  I
don't believe in the answer "use /NoWarn" either, since warnings are
important.  The way to make this warning go away is to clean up your
code.  I'm sure you can find a way to make this routine return a
consistent result, either by breaking it into two routines (which it
sounds like it really is, anyway) or having a second routine to call
this one and explicitly convert the results to the proper form.

You'll have to talk long and hard to convince me that there's no better
way to get your job done.
CC:     roger@ll-sst.arpa,
	info-vax@sri-kl.arpa