× 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: What bugs you about KLISTs in RPG IV?
  • From: Gwecnal@xxxxxxx
  • Date: Mon, 14 Jun 1999 12:14:31 EDT

In a message dated 99-06-14 12:08:13 EDT, you write:

> 1) What are  the top three things that bug you about programming
>     compound keys in RPG?
>  
>  2) Would KLISTs in D-Specs fix any of those things?
>  
>  3) What would make compound keys easier in RPG?

The only thing that bothers me about klists is that they have to be defined 
somewhere other than the definition section of my program!  Now with ILE and 
procedures, I put ALL my field and parameter definitions in the D-specs.  Now 
there is no hunting through the code to find where a field is defined - 
EXCEPT klists.  If you you can't d-spec a klist, how about allowing index 
access through a data structure?  At least then I will be able to keep my 
defintions together.  TIA
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* 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          *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *


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.