NetRexx 3 improvments: Value-lists

[Thomas.Schneider.Wien]

  7.) As I did work for General Electric Information Services (GEISCO),
which did provide
something like the *Internet* decades decades ago (I did startthe 1964,
I think)
but lost the game as they have been too stupid to quickly react:

I'm also proposing a syntax for VALUE-Lists:

7.1) a Value List is either a simple value list (also called
Enumeration), or a Value RANGE list.
7.2) A Value List becomes a value-range-list if (and only if) any memebt
of the list is a range
7.3) Within the value list, *NO variables* are allowed
7.4) Values may be entered unquoted, unless a delimiter is used.
7.5.) When a delimiter is used, it must be quoted
7.6) I am proposing the COLON (:) as the commonly used range indicator.

thus, the following would be proprose NetRexx 3 syntax:

     i =int i {3,5,7,9,11,12:13,17}
detto:

    answer={YES,NO}

Quotes may be omitted within the braces, when not necessary, because
delimiters are used.

The two examples above will form (simple) value lists

8.) Value-range-lists:

     a typical value Range list will be:

        a={1,3,7:9,12,13:44}

     We must still decide whether we should allow the HYPHEN (instead of
the COLON)
as the range separator (or both the hyphen for numerics and the colon
generally)

Comments are welcome :-)

9) Usage of value lists of value range-lists

      typical usages might be

          a=ask
          if a \= {YES,NO} then error('invalid answer')

Comments are welcome!
Tom.

--
Thomas Schneider Projects ReyC & LOGOS on www.KENAI.com
_______________________________________________
Ibm-netrexx mailing list
[hidden email]

[Jeff Hennick]

  With out yet endorsing this idea, I have some questions/suggestions.

On 8/25/2010 10:40 PM, Thomas Schneider wrote:

>  7.) As I did work for General Electric Information Services (GEISCO),
> which did provide
> something like the *Internet* decades decades ago (I did startthe
> 1964, I think)
> but lost the game as they have been too stupid to quickly react:
>
> I'm also proposing a syntax for VALUE-Lists:
>
> 7.1) a Value List is either a simple value list (also called
> Enumeration), or a Value RANGE list.
> 7.2) A Value List becomes a value-range-list if (and only if) any
> memebt of the list is a range
> 7.3) Within the value list, *NO variables* are allowed
> 7.4) Values may be entered unquoted, unless a delimiter is used.
> 7.5.) When a delimiter is used, it must be quoted
> 7.6) I am proposing the COLON (:) as the commonly used range indicator.
>
> thus, the following would be proprose NetRexx 3 syntax:
>
>     i =int i {3,5,7,9,11,12:13,17}
> detto:
>
>    answer={YES,NO}
>
> Quotes may be omitted within the braces, when not necessary, because
> delimiters are used.
>
> The two examples above will form (simple) value lists
>
> 8.) Value-range-lists:
>
>     a typical value Range list will be:
>
>        a={1,3,7:9,12,13:44}

Must they be integers, or can real numbers (2.5, 3E4) also be used?
>
>     We must still decide whether we should allow the HYPHEN (instead
> of the COLON)
> as the range separator (or both the hyphen for numerics and the colon
> generally)
Drop the hyphen idea; it is ambiguous.  Is {-3-1} really {-3:-1} or
{-3:+1} ?  Even if one is "defined" as right, it is not obvious to a
reader.  That is one of the design requirements of REXX and one of the
great reasons for its continuing success nearly 30 years later.

If real numbers are allowed as simple values (and I think they should)
what does that imply for ranges?  Are all real values between the
inclusive range ends valid? I can think of uses for each case.  Should a
second range separator be introduced?

>
> Comments are welcome :-)
>
> 9) Usage of value lists of value range-lists
>
>      typical usages might be
>
>          a=ask
>          if a \= {YES,NO} then error('invalid answer')
>
> Comments are welcome!
> Tom.
>

_______________________________________________
Ibm-netrexx mailing list
[hidden email]

[Thomas.Schneider.Wien]

  Am 26.08.2010 05:13, schrieb Jeff Hennick:
>  With out yet endorsing this idea, I have some questions/suggestions.
Hi Jeff,
     I (and maybe/hopefully the whole group)

... would like to know your ideas !!

Hence, please simply write them down and publish them here ...
As a matter of fact back in the 60' and 70's of the past century I did
work at General Electric Infromation
Services (GEISCO). At those times, we have beem very successful selling
the MARK III service:

Why: because we did implement applications with varios 4th Generation
Languages as TABOL, DMS,
and or LOGOS (which I did personally write, and which has been bought
1984 by GE, but *only to get it **not** on the market.

A personal de-motivation, you can imagine :-)

I'm currently missing in that whole Object-Oriented discussion the whole
impact which 4th generation languages
did have in those times.

And the ideas all they introduced....

I'm now so long working in the IT ...

Currently, I am trying to complete my PP project (project 'PP' on
www.kenai.com):

TRANSFORM  Rexx, ooRexx, NetRexx, PL/I, and COBOL programs from one
*source-language*
to the desired *target-language*

My previous cade was all written in IBM compiled Rexx.

Using my currently private copy of Rexx2Nrx, I did translate it now all
to NetRexx.

*NOT yet fully Object oriented*, I must admit, as so many ports have
been involved ...

But it seems to working again, I think.

Tom.
===============================================================================================

>
> On 8/25/2010 10:40 PM, Thomas Schneider wrote:
>>  7.) As I did work for General Electric Information Services
>> (GEISCO), which did provide
>> something like the *Internet* decades decades ago (I did startthe
>> 1964, I think)
>> but lost the game as they have been too stupid to quickly react:
>>
>> I'm also proposing a syntax for VALUE-Lists:
>>
>> 7.1) a Value List is either a simple value list (also called
>> Enumeration), or a Value RANGE list.
>> 7.2) A Value List becomes a value-range-list if (and only if) any
>> memebt of the list is a range
>> 7.3) Within the value list, *NO variables* are allowed
>> 7.4) Values may be entered unquoted, unless a delimiter is used.
>> 7.5.) When a delimiter is used, it must be quoted
>> 7.6) I am proposing the COLON (:) as the commonly used range indicator.
>>
>> thus, the following would be proprose NetRexx 3 syntax:
>>
>>     i =int i {3,5,7,9,11,12:13,17}
>> detto:
>>
>>    answer={YES,NO}
>>
>> Quotes may be omitted within the braces, when not necessary, because
>> delimiters are used.
>>
>> The two examples above will form (simple) value lists
>>
>> 8.) Value-range-lists:
>>
>>     a typical value Range list will be:
>>
>>        a={1,3,7:9,12,13:44}
> Must they be integers, or can real numbers (2.5, 3E4) also be used?
>>
>>     We must still decide whether we should allow the HYPHEN (instead
>> of the COLON)
>> as the range separator (or both the hyphen for numerics and the colon
>> generally)
> Drop the hyphen idea; it is ambiguous.  Is {-3-1} really {-3:-1} or
> {-3:+1} ?  Even if one is "defined" as right, it is not obvious to a
> reader.  That is one of the design requirements of REXX and one of the
> great reasons for its continuing success nearly 30 years later.
>
> If real numbers are allowed as simple values (and I think they should)
> what does that imply for ranges?  Are all real values between the
> inclusive range ends valid? I can think of uses for each case.  Should
> a second range separator be introduced?
>>
>> Comments are welcome :-)
>>
>> 9) Usage of value lists of value range-lists
>>
>>      typical usages might be
>>
>>          a=ask
>>          if a \= {YES,NO} then error('invalid answer')
>>
>> Comments are welcome!
>> Tom.
>>
>

--
Thomas Schneider Projects ReyC & LOGOS on www.KENAI.com
_______________________________________________
Ibm-netrexx mailing list
[hidden email]