interpret procedure expose ...

Thread View: bit.listserv.rexxlist

2 messages

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

2 total messages Started by Rich Winkel Mon, 15 Jun 1992 20:07

#201

Author: Rich Winkel
Date: Mon, 15 Jun 1992 20:07

5 lines
879 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?

Rich

Re: interpret procedure expose ...

#200

Author: David Barr
Date: Mon, 15 Jun 1992 21:30

34 lines
1514 bytes

In article <REXXLIST%92061516145008@UGA.CC.UGA.EDU>, Rich Winkel
<MATHRICH@MIZZOU1.BITNET> says:

>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 new Rexx spec is slightly different with CMS 7. A "procedure"
statement may appear only after the word "exit".  Well that's not quite
true, technically you can only use the keyword "procedure" when
executing a "call" or function statement.  In other words, you can't have
procedures in the middle of a program block.

Before, you could have:

/**/
statements...
foobar: procedure
....
return

now, you must have:

/**/
statements...
...
call foobar
...
exit
foobar: procedure
...
return

--Dave

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