Re: Additional RPGLE Enhancement Requests

Hans,

>> 5.  Permit INDIVIDUAL fields to be externally defined without having
>>     to define an externally defined data stucture.
>>
>>     D   Temp2   S      like(field2:filename1:optrecfmt1)
>>     D           DS
>>     D   Temp4          like(field4:filename2:optrecfmt4)
>>     D   Temp3          like(field3:filename1:optrecfmt1)
>>
>>     where filename1 and filename2 are not used at all in the program.
>
>I also push for this when I can.  But the alternative of defining fields
>LIKE subfields of a BASED EDS is already available.

 But it's problematic depending on that implementation, since we are bound
by DS limitations, specifically conflicting variable names.  If the EDS
contains the same variable name as a variable in another DS, there is a
problem.  Or even worse, if the variable has different attributes, etc.  We
are not always dealing w/ "clean" databases and often enough have to marry
two different systems.

 I vote strongly for individual REF/REFFLD availability.


>> 10.  PREFIX(M2:2) is wonderful.  I can't tell you how may people asked
>>      for a suffix capability in the RPG IV seminars I have done.  Most
>>      people name every field in a file using the same characters, e.g.
>>      MBNAME, MBCITY, MBDATE, etc.  I had no idea how many people use
>>      the standard NAMEMB, CITYMB, DATEMB, etc.  How about the following:
>>
>>      PREFIX(M2:2:*SUFFIX) to replace the last 2 non-blank characters
>>
>>      or PREFIX(M2:0:*SUFFIX) to add the suffix after the last non-blank
>>      character.
>
>Hmmm!  This suggestion is new to me!  Someone else suggested a SUFFIX
>keyword.  Another alternative is to allow negative values as the 2nd
>parameter to indicate suffix.

 I like the SUFFIX() keyword.  It's simple and straightforward.


>I like GOTO *ENDSR.  I know one or two structured programming purists
>may object, but I know how darn convenient it is to leave a "structured"
>construct prematurely.

 GOTO *ENDSR or LEAVSR or EXITSR or whatever method; just put it in!

 --------------------

 BTW, what would it take to get approval for XOR to be put into the next
release?

 -mark

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *