|
> -----Original Message----- > From: Bob Cozzi [SMTP:cozzi@rpgiv.com] > Sent: Thursday, July 29, 1999 8:18 PM > To: RPG400-L@midrange.com > Cc: one List > Subject: RPG IV and CF-spec "keep it IBM" > > > So I ask you, if you do NOT care if the CF-spec every sees the light of > day, > or DON'T want the CF-spec, to voice your opinion now. > I feel we need an architecture for RPG. We need many poorly designed > features corrected, we need consistent designs and several new features > before we effectively turn RPG IV into CL II. > Let me know what you think. > Bob Cozzi > [Hatzenbeler, Tim] I think you have a good idea here, I would like the ability to run commands straight from RPGIV or (CL II) without having to use the qcmdexc. what do you think cf select cf when choice ='5' cf dspsplf cf when choice = '6' cf dspsyssts cf endsl I think a marriage between RPG IV & CL, would be fantastic. For OVRDBF, this would be cool and a lot more maintainable since you would not have to worry about a front end CL to handle the Sort Criteria, your program could dynamically set up the sort's inside of the RPG, I know you can do this now, but I'm just talking about readability. F Names if K Disk Usropn cF Ovrdbf (Names) share (*yes) ........ cf open Names cf dou %eof(names) cf read names cf enddo cf close names cf dltovr (Names) I know you were being sarcastic but you did open a Pandora's box in my mind when you suggested CL II. just my 2 1/2 cents. Tim +--- | 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 +---END
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.