|
Duane, You think it's brilliant that EXPORT(*ALL) not only exports procedures in any module I've got in my MODULE list but also any subprocedure you might have linked into your service program from the binding directory? You think it's brilliant that I have to use some oddball configuration format (binding source) to get around this problem? That's an odd definition of brilliant. Binding source is great if you only want to export some procedures but not others. There's also other uses for binding source like maintaining a procedure's entry point in the service program between versions. All well and good but EXPORT(*ALL) shouldn't apply to modules in the binding directory. If I want to export something from a module make it more explicit. Should have made me place it in the MODULE list before I can export it from the service program. Paul
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.