|
> From: Mike Haston > If you need /free and /end-free tags "all over the place" > then you couldn't use this all source alternative anyway, > could you? But if your code does fall into this criteria, > then you'd just have to use one /free and one /end and that > doesn't seem like too much coding. Or am I missing something? In addition to the mainline, there is a pair of tags required within each sub-procedure. In my opinion, the tags clutter up the code needlessly, since I don't write mixed-form source members. It's not something that I would expect IBM to spend a lot of time on, but it *seems* easy enough to eliminate the need for them, so I figured why not throw it out there. The worst that can happen is that, well, nothing happens. John Taylor
This mailing list archive is Copyright 1997-2026 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.