|
>> You can't do it that way. >> You need to place your functions into a service program. I agree that for most cases a Service program is the way to go - after all that is what they were designed for. However, your basic "You can't do it ..." statement is incorrect. I can and have done it several times. In fact it is not even necessary to bind the modules - you can treat _any_ PGM object as a service program if you wish. The basic requirement is that you have a means to call the PGM and it responds by supplying one or more procedure pointers to its internal procedures. You then make subsequent calls via those procedure pointers. We have used the technique a number of times to get the effect of a dynamically loaded "service program" - it also allows for semi) dynamic swapping of the "service program". Not that there are APIs for dynamically resolving the procedures in a Service Program, this is not needed as often, but it has its uses. Jon Paris Partner400 www.Partner400.com www.RPGWorld.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.