|
In a message dated 11/20/99 3:49:07 PM Pacific Standard Time, dmorris@plumcreek.com writes: << Opens will also be shared which may require some restructuring of your applications. Your may also want to spend some time identifying the common parts of these programs and supporting them in separate, shared routines. Converting to sub-procedures is probably a lot of work, *NEW may be a good starting point/compromise. >> All of our opens are shared anyway. But I am leaning towards *NEW for just the reasons you state. The release after this release, I might look into breaking each part of the program into subprocedures, but not now. Ron +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.
midrange.com
