|
Oh, well, yeah, that I knew. 8-) And I think he's right, it should be in the D specs. One of the things I live about RPGIV is being able to declare the S type of the D spec for all my variables. Now I don't have to search all over the code to find out how a variable is declared, I know where it is. And there are no longer problems with declaring a variable twice. When I first started to program I hated having to declare variables (ala Cobol, Pascal, etc..) and thought it was a waste of time. Until the first time I got so confused as to how a variable was defined. I then started declaring my variables in Basic, where it wasn't required at all. I think they did a good thing by allowing the use of the D spec to declare variables, and, yes, I think that all types of declarations should go there, such as KLIST. I mean, what would be so hard to use a DS structure as, say, a KL structure for keys? But then, are KLISTs even *really* required? Why can't we just use a named DS structure? Or are they saved differently in memory somehow? yes, I know we can't use them because it won't work, my question is, why don't 'they' get it to work? Regards, Jim Langston HwaRangRon@aol.com wrote: > Brad, > I think he meant dead in the since the code is not actually executed. I think >he's right, KLISTS belong in D specifications, not C specs. > > Ron > > In a message dated Fri, 10 Sep 1999 9:52:35 AM Eastern Daylight Time, >"Stone, Brad V (TC OASIS)" <bvstone@taylorcorp.com> writes: > > > A "dead" command? Oh boy.. here we go again. > > > > I suppose ADD is a dead command too because we have eval. Well, what if you > > are incrementing a counter that you want to loop back to zero after it > > maxes? With eval, error. With add, overflow and no problems. > > > > Please, don't start calling commands dead. It's silly. RPG is supposed to > > be a dead language. (haha!) But it's still used. > > > > Bradley V. Stone > > BVS/Tools > > http://www.bvstools.com > > > > > > > > > > > -----Original Message----- > > > From: rbrightman@amclog.com [mailto:rbrightman@amclog.com] > > > Sent: Friday, September 10, 1999 8:01 AM > > > To: RPG400-L@midrange.com > > > Subject: Key List in 'D" spec > > > > > > > > > > > > > > > Does anybody know why RPG designers don't have 'key lists' in > > > 'D' specs? It > > > seems to me that 'C' specs should only have "active" commands > > > in them. Key list > > > (KLIST) is a dead command. > > > > > > Rick, Atlanta > > > > > > > > > +--- > > > | This is the RPG/400 Mailing List! > > > | To submit a new message, send your mail to RPG400-L@midrange.com. > > > | To subscribe to this list send email to RPG400-L-SUB@midrange.com. > > > | To unsubscribe from this list send email to > > > RPG400-L-UNSUB@midrange.com. > > > | Questions should be directed to the list owner/operator: > > > david@midrange.com > > > +--- > > > > > +--- > > | This is the RPG/400 Mailing List! > > | To submit a new message, send your mail to RPG400-L@midrange.com. > > | To subscribe to this list send email to RPG400-L-SUB@midrange.com. > > | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. > > | Questions should be directed to the list owner/operator: >david@midrange.com > > +--- > > +--- > | This is the RPG/400 Mailing List! > | To submit a new message, send your mail to RPG400-L@midrange.com. > | To subscribe to this list send email to RPG400-L-SUB@midrange.com. > | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: david@midrange.com > +--- +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-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 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.