|
Hey, maybe have the precompiler search for BEGSR's and kill the compile? Rob, it's not that I'd never RETURN from within a subroutine. It's just that I'd never tolerate a one-statement subroutine. Never. Don't even go there. GA --- rob@xxxxxxxxx wrote: > And that's a good way to evolve. > > Stop using subroutines, no matter how simple. And use subprocedures > instead. While the subroutine may be too simplistic to make sense to > bother with the PR's and PI's it's a good discipline to stick to it as a > "Commandment from God" for two to three months just to get into practice. > And then, only then, go back to using subroutines when it's really > simplistic. Or you have some special need like having RETURN exit the > program and not just the subprocedure. (There are those who feel that > exiting a program from a subroutine is a violation of structured > programming and is punishable by (your humorous situation here)). > > Then as you evolve you can decide which subprocedures might make sense to > move to a service program. > > Rob Berendt __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com
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.