interpret procedure expose ...

Thread View: bit.listserv.rexxlist

1 messages

[T] Back to Threads [V] Tree View [G] Group Articles

1 total messages Started by BJ VanDewater Tue, 16 Jun 1992 09:32

#54

Author: BJ VanDewater
Date: Tue, 16 Jun 1992 09:32

17 lines
1621 bytes

>>  this used to be a valid statement in vm-rexx.  Now that we've
>>  upgraded to cms 7, it triggers an "Unexpected PROCEDURE" error,
>>  even when it's the first statement in the subroutine.  Is this a
>>  bug, or a feature?

     The fact that this used to execute was not in accordance with the
language definition.  Quoting from Mike Cowlishaw's "The REXX Language"
"If a PROCEDURE instruction is included, it must be the first instruction
executed after the CALL or function invocation - that is, it must be the
first instruction after the label."
     There is nothing in the language definition that requires an EXIT
instruction (or a RETURN instruction for that matter) to precede the
PROCEDURE instruction, though it is often a good idea so that the
code does not accidentally fall into an unexpected routine.

          BJ VanDewater  REXX Compiler Development
                         Vienna Software Development Laboratory

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads