Re: What bugs you about KLISTs in RPG IV?

Dan Bale wrote:
> 
> Programmers are also able to throw KLISTs all over the source now (and, boy, 
>do
> they ever!).  What happens more in maintenance?  A) Keys to a file changing?  
>or
> B) trying to find the KFLD fields of the KLIST that is associated with a CHAIN
> or a READE that is causing problems?  In all the environments I've been in, 
>99%
> of the time it's "B".

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

Or, if you use LPEX, ctrl-f.

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.

Standard tenent in coding:  one op, one place, one change.

-- 
===========================================================
R. Bruce Hoffman, Jr.
 -- IBM Certified AS/400 Professional System Administrator
 -- IBM Certified AS/400 Professional Network Administrator

"The sum of all human knowledge is a fixed constant.
    It's the population that keeps growing!"
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* 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          *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *