Re: What bugs you about KLISTs in RPG IV?

Bruce,

I know this dead horse is getting pretty well beaten ;-), but.....

>>You know, searching for a klist is only an F16 key away.<<

Yeah, but why search for it when you have it right with ONE op code, the chain
or reade?

>>Just about any editor can find the klist.  The problem is that you are
suggesting that we remove the klist and scatter the information across the
program instead of just one place.<<

What is the "information"?  The key values?  Tell me from the two examples below
which is more "scattered".

Example 1:
 At the top of the C-specs:
    Key1      Klist
              Kfld           CoNo55
              Kfld           OrdN55
              Kfld           OrdL55
 ... hundreds of lines later, in a subroutine far, far away...
              Eval     CoNo55 = L#CoNo
              Eval     OrdN55 = OrdN50
              Eval     OrdL55 = OrdL50
    Key1      Chain    File55                  99

Example 2:
     chain   File55(L#CoNo: OrdN50: OrdL50)

You know what my choice will be.  One op code, one place, one change.

- Dan Bale





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