|
John, I know exactly what you are talking about and I too would like to see qualified procedure names. This would allow a sort of object oriented approach to creating service programs. I could have a service program named Invoice and another called BillOfLading, they both could have a procedure called Print. I would much prefer this rather than having to name each procedure something like InvoicePrint. Unable to have qualified procedure names really disappointed me when I first started creating service programs. I believe the reason you don't see may complaining about this is there aren't that many people using service programs and procedures like they really should be. I think procedures and service programs are one of the greatest features added but it is very difficult to convince the typical RPG programmer of how great they are. Scott Mildenberger > -----Original Message----- > From: John Taylor [SMTP:jtaylor@rpg2java.com] > Sent: Wednesday, February 27, 2002 12:23 PM > To: rpg400-l@midrange.com > Subject: Re: MOVE opcode in freeform (was Strange behavior w/%editc) > > Hans, > > I can appreciate where you're coming from. The available resources are > limited, and this particular wheel hasn't been squeaking very much. > > Personally, I'm a little perplexed as to why I seem to be the only one > that > ever brings it up. Maybe it's because there just aren't that many of us > doing ILE development yet. Or maybe the concept hasn't been clearly > explained to those unfamiliar with languages other than RPG. Is anyone on > the list unsure of what we're talking about here? > > > John Taylor > > ----- Original Message ----- > From: <boldt@ca.ibm.com> > To: <rpg400-l@midrange.com> > Sent: Wednesday, February 27, 2002 11:26 AM > Subject: Re: MOVE opcode in freeform (was Strange behavior w/%editc) > > > > John wrote: > > >One of the things preventing this from happening is the limitations of > the > > >language with respect to the shared namespace. In order for me to use a > > >publicly available service program with RPG, I have to hope that the > > >author's naming convention doesn't clash with my own internal > standards. > > >Qualified procedure names would go a long way towards making your wish > > come > > >true. > > > > I would accept that argument IF people complained about namespace > > collision. > > > > I do agree that there should be some mechanism to qualify > > procedure names, but until there's a consensus that a solution is > > needed, we can't really justify the enhancement. > > > > No, I think you have to look elsewhere for excuses for the lack > > of a "Comprehensive RPG Archive for Modules and Procedures". > > (Please someone come up with a better acronym than that!) > > > > Cheers! Hans > > > > Hans Boldt, ILE RPG Development, IBM Toronto Lab, boldt@ca.ibm.com > > > _______________________________________________ > This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list > To post a message email: RPG400-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l > or email: RPG400-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/rpg400-l.
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.