|
>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. Ran into this myself - with my own code! What I do is name all of my exported procedures the name of the module + the procedure. ADR106_myProc() phil > >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
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.