× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Missing from RPG/LE
  • From: Rob Berendt <rob@xxxxxxxxx>
  • Date: Fri, 25 Sep 1998 8:27:05 -0500

I think that you bring up some good points.  And there might be an argument 
that since ILE RPG allows
 you to create your own functions via procedures you should be able to do it 
yourself.  I find that mildly
 acceptable in the short term.  However I agree that the language should 
support these.  Hopefully the
Toronto lab picks up on these via the mailing list.  There is an official way 
to go through to request
enhancements however, (other than COMMON).  This process used to be called a 
PASR.  I think that
it is called a REQUEST DATA form, or a Request for Change, now.  They rotate 
the person in charge
of this on an extremely frequent basis.  The last person that I talked to that 
ran this was Lee Eastman
at 507-286-6784.  Perhaps you might call him.  I have submitted some changes 
this way and have
seen them come to fruition.




jteff19@idt.net on 09/25/98 12:08:00 AM
Please respond to MIDRANGE-L@midrange.com@Internet
To:     midrange-l@midrange.com@Internet
cc:      
Subject:        Missing from RPG/LE

I appreciate how much more readable code is in RPG/LE than any other flavor of
the language. There is one area though that I think a much better job could have
been done. I think that having a %Range and %List BIFs would really help
cleanup coding.

  I would write:

     C                                  If              DateEntered >= 980101 
and
     C                                                  DateEntered <= 980131

  Instead I could write

     C                                  If              DateEntered = 
%Range(980101 980131)

  Or I would write:

     C                                 If              ItemStatus <> 'D' and 
ItemStatus <> 'O' and
     C                                                 ItemStatus <> 'P'

  Instead I could write:

    C                                  If               ItemStatus = Not 
%List('D' 'O' 'P')

   Or, even better:

    D Deleted                               C                              'X'
    D Obsoleted                           C                              'Q'
    D Prototype                            C                              'S'

    C                                  If              ItemStatus = Not 
%List(Deleted Obsoleted Prototype)

This code would become even more readable and thus more maintainable. In fact, 
many
of the BIFs available in SQL look like good possibilities.

I really do like what has been done to the language and find that writing in 
RPG3 (aka
RPG/400) is becoming as untasteful as writing in RPG2.

Joe Teff

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.