|
This is an interesting issue. It sounds like web domain naming to me... get the "dot com" before the other guy: "ship the procedure name before the other guy". Hmm??? Well, I suppose it is an issue if I create a procedure named XYZ and it is included in my RPG ToolKit, and then John creates another service program and includes a procedure named XYZ. Now the only conflict is if the customer wants to use both XYZ procedures in the same piece of code, otherwise there's no issue. Yep, that could be a challenge coming down the road. Bob Cozzi Cozzi Consulting www.rpgiv.com -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of John Taylor Sent: Friday, June 20, 2003 12:53 PM To: 'RPG programming on the AS400 / iSeries' Subject: RE: RE: binder language, binding directories, bind by copy/reference > From: jrc@xxxxxxxxxx > I'll keep my comments short and cut right to the chase: we > need procedure overloading. If a procedure had real > signatures based on the name, parm list (including sizes and > types), and return value, then we could hash those signatures > to create the service programs. RPG has bifs with > overloading (like %date) so why can't we have it in the language? Amen! And while we're at it, let me once again beg for qualified procedure calls. I'm tired of having to assign meaningless prefixes to my procedure names in the hope that they won't conflict with existing code at customer sites. Since so few sites actually use ILE, this has been workable so far, but I don't expect my luck to hold out forever. If you think about it, what are you going to do when you release a service pgm with procedure xxMyProc(), only to find some other vendor had the same naming convention, and your customer now can't use those service programs together. If we ever reach widespread use of ILE, things are going to get ugly. Regards, John Taylor _______________________________________________ This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx 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.