OREXX does the same thing. I don't recall that being vakid syntax, but it sort
of makes sense.
/* test continued comment */
say 'foo'/*,
*/'bar'
say 'foo'/**/'bar'
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
________________________________________
From: IBM Mainframe Discussion List [[email protected]] on behalf of
Paul Gilmartin [[email protected]]
Sent: Sunday, June 27, 2021 2:45 PM
To: [email protected]
Subject: Re: Coding for the future
On Sun, 27 Jun 2021 11:01:55 -0700, Charles Mills wrote:
>I tend to think of the insertion of blanks to be unfortunate.
>
Alas, in Regina, with no blanks in the source:
trace R
say 'foo',
'bar'
2 *-* say 'foo' 'bar'
foo bar
607 $
However:
trace R
say 'foo'/* ,
*/'bar'
2 *-* say 'foo'/* */'bar'
foobar
>It is great if you are wanting to demonstrate the incredible simplicity of
>Rexx:
>
>Say Hello World
>
I think the case conversion is unfortunate.
>But I think if you want a blank between the two halves of the "continued"
>(in quotations) literal then just code it.
>
>Foo = "blah blah_" || ,
> "blah blah"
>
"_" ==> " " ???
>If you want the code to run on different platforms you might just have to
>code for that. Would not be the first time for either of us. For most of us.
>
For ugly example:
trace R
parse upper source OS .
select
when OS=='TSO' then NL = '15'x;
when OS=='UNIX' then NL = '0A'x;
when OS=='WINDOWS' then NL = '0D0A'x;
otherwise signal Unknown_OS;
end
/*
Is there a way to do this without enumerating
all supported operating systems, akin to C's:
char *NL = "\n";
??? */
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
