|
> From: Lim Hock-Chai > > true. However, why take the risk of have to rewrite something that > already tested? Especially when the sub-routine exsr to another sub- > routine.... Then you'll really having fun converting them. > > Also what if in those panel sub-routines, you need to make sure changes > and this time local variables make sense. When would local variables make sense? These are the panel subroutines for an application controller. It seems to me that you're making up hypothetical cases to try and justify a pretty inflexible position ("SUBROUTINES ARE BAD!"), rather than looking for reasons why someone would use one or the other. And if all it takes to turn a subroutine into a procedure is a few lines of code, I guess I can live with that if I ever need to do it. But I've been writing this sort of application for many years now, and I've never had to reuse a panel routine. Joe
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.