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!ulysses!mhuxr!ihnp4!ucbvax!info-vax From: info-vax@ucbvax.ARPA Newsgroups: fa.info-vax Subject: Possible VAX/VMS PL/I Bug involving return values? Message-ID: <4751@ucbvax.ARPA> Date: Tue, 12-Feb-85 03:08:16 EST Article-I.D.: ucbvax.4751 Posted: Tue Feb 12 03:08:16 1985 Date-Received: Wed, 13-Feb-85 01:38:31 EST Sender: daemon@ucbvax.ARPA Organization: University of California at Berkeley Lines: 28 From: Jerry BakinI compiled the following PL/I program under VAX/VMS, and an identical one under Multics (except quotes for apostrophes). The VMS compiler yielded the results below. The Multics compiler compiled code which, when executed, gave the "obvious" results. This seems to be a VMS compiler bug, but could it be a PL/I subset G versus complete PL/I issue? 1 test_0: procedure returns (bit (1)); 2 1 3 1 return ('0'b); %W, Implicit conversion of the return value, a constant '0'B, to the function type CHARACTER. 4 1 5 1 test_1: entry returns (char (1)); 6 1 7 1 return ('0'); %W, Implicit conversion of the return value, a constant '0' to the function type BIT. 8 1 end; I think these error messages are great! Jerry Bakin