|
Thanks, Simon! Somehow I missed that. Simon wrote: Finally! a question hidden in all the opinionated guff. You can do this. EXPORT simply makes the procedure visible outside the module. It does not automatically make it visible outside the service program containing the module. You must make the procedures part of the public interface using binding source or the awful EXPORT(*ALL). So, o procedures without EXPORT are private to the module o procedures with EXPORT are protected (visible within the bind unit) but also candidates for public consumption o procedures listed in binding source are public Regards, Simon Coulter.
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.