ReyC 1.0.0 -- some additions of me to the NetRexx Language

[ThSITC]

May I also add, please, without disturbin any/all of you, that I did
meanwhile
implement 'Rey' as a language, with the follwing new features (as
compared to NetRexx:

-- implement multiple assignment:

      a,b,c = expression

-- implement new verbs SHOW, ACCEPT (for screens), and REPORT, PRINT,
TITLE, FOOTING,
etc (for PRINTED, Formatted, Reports)

e.g.: SHOW a,b,c       does show:

      a ................: a
      b.................: b
      c.................: c

in the normale, CONSOLE Mode.

When using ReyScreen instead of ReyMsg, the respective statements are
switching to
the well known Java SWING behaviour. e.g. Screens are built, and the
operator wiil
change to a SCREEN operating mode :-)

The already implemented 'askfor' method, as documented years ago in the
Rexx2Nrx
run-time manual (www.Rexx2Nrx.com/RunTime/ReyMsg   function askfor) is
used for
this purpose.

i.e.:

    name = askfor('Name')
    gender=askfor('Gender','male/female')

etc.

The advantage of this approach (as I see it) is:

- You might develop an application very quickly in the CONSOLE mode,
test it, and, *when ok*, switch to *SCREEN Mode* :-)

-- Before I do make this msg too long: :-(

I did implement my own language enhancements to NetRexx, would like to
disclose
those on this list, adn *discuss* it, without *boring* and *frustrating*
anybody.

Thomas.

PS: I used to work with a lot of so-called 4GL Languages, decimals ago,
and I do like *rich* languages (and do *not* like to interface to
Microsoft Excel
to perform the simple task to get a FORMATTED output :-(

Full Stop. Thomas, again

:
--
Thomas Schneider (www.thsitc.com)
_______________________________________________
Ibm-netrexx mailing list
[hidden email]

[alansam]

On 12 April 2011 12:47, Thomas Schneider <[hidden email]> wrote:

May I also add, please, without disturbin any/all of you, that I did meanwhile
implement 'Rey' as a language, with the follwing new features (as compared to NetRexx:

-- implement multiple assignment:

    a,b,c = expression

Discussed many times and every time rejected for very sound reasons not least of which is that it departs from the Rexx family of languages.
 

-- implement new verbs SHOW, ACCEPT (for screens), and REPORT, PRINT, TITLE, FOOTING,
etc (for PRINTED, Formatted, Reports)

These do not need to be part of the language.  They can and should be provided as library classes that programmers can choose to exploit if they wish.  The compiler shouldn't need to be involved with generating and syntax checking this type of code.
 

The already implemented 'askfor' method, as documented years ago in the Rexx2Nrx

Again; this can be easily supplied via extension libraries for programmers to use or not as they wish.  There's no need for this type of thing in the base language, it's just code candy.

Alan.

--
Can't tweet, won't tweet!

_______________________________________________
Ibm-netrexx mailing list
[hidden email]

[ThSITC]

Hi Alan,
   1.) Thanks for your valid response :-)
   2.) I do have actually an opposite OPINION (personally)
   3.) As shorter the code I do have to write to accomplish a task, as quicker I can develop my
new soft <grin> <as Mark, author of ooDIALOG, would say>

   4.) By the way, I did also implement:

y=4
x=3
y +=x

... which does give: 7 (surprise, surpise ;-)

My hope:

Please let us KEEP this discussion OPEN :-)
Thomas.
===============================================================================
Am 12.04.2011 22:11, schrieb Alan Sampson:

On 12 April 2011 12:47, Thomas Schneider <[hidden email]> wrote:

May I also add, please, without disturbin any/all of you, that I did meanwhile
implement 'Rey' as a language, with the follwing new features (as compared to NetRexx:

-- implement multiple assignment:

    a,b,c = expression

Discussed many times and every time rejected for very sound reasons not least of which is that it departs from the Rexx family of languages.
 

-- implement new verbs SHOW, ACCEPT (for screens), and REPORT, PRINT, TITLE, FOOTING,
etc (for PRINTED, Formatted, Reports)

These do not need to be part of the language.  They can and should be provided as library classes that programmers can choose to exploit if they wish.  The compiler shouldn't need to be involved with generating and syntax checking this type of code.
 

The already implemented 'askfor' method, as documented years ago in the Rexx2Nrx

Again; this can be easily supplied via extension libraries for programmers to use or not as they wish.  There's no need for this type of thing in the base language, it's just code candy.

Alan.

--
Can't tweet, won't tweet!

_______________________________________________
Ibm-netrexx mailing list
[hidden email]