|
Dan wrote: >Since QA testing is a significant undertaking in this >shop, anytime we can plug in discrete modules into a >new application, or modify one module in an application >that uses several modules, makes for easier and faster >testing. Does that adequately answer your "foot in mouth" >argument, Buck? <g> No, my foot might still be firmly lodged. My point is that my view of procedures is that they are small: tiny, even. A proc fits on one page/display. They're easy to understand at a glance. Programs are more complex, they are built up from my procedure-BIFs, and take time to comprehend. You can substitute the word 'program' or 'procedure' for your use of the word 'module' above and have the same effect. In fact, programs may be a better fit for you if you are using bind by copy instead of service programs, but that borders on a lecture, I guess. --buck
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.