|
quote> Actually, I have always thought it bad practice to explicitly refer to a library in a program, but maybe thats just me. ..I agree that using the library list instead of referring to specific libraries was always the best programming practice. You can mix and match releases, mods, this and that, much easier. With a minimum effort you can set it up to put minor (but maybe important, urgent) new fixes in on the fly while people are still working on the older ones, if it's not a showstopper. A technique like this is good for menu programs with their displays (another story really)... The reason I think a good design for productivity is to have QTEMP at the top of the user library list, is for all the above reasons, you can put anything in there, and if your programs use the *LIBL per normal, that's the one they pick up. The overrides introduce more levels of complexity, especially with activation groups around, and the client-server model for applications (using queues too!), and so on. BUT I have seen QTEMP in so many places in the library list that I have gotten into a CYA habit of just using the override method. Haven't yet had the opportunity to design a shop setup.. :-) --Alan
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.