|
> > @#$*&!!! These drive me crazy! I realize, from the list response, that > I am likely in the minority. I like to think there's more of a balance > between one-line subroutines and monolithic programs. Oh, and thanks > for not lecturing. <g> > FWIW, Dan, I agree with you. There does reach a point where breaking things up into smaller pieces actually makes the code harder to follow. It can also create 'spaghetti code' or code that you have to constantly jump around in the source (or worse, in multiple members) to follow the code. Anything in a procedure should be a black-box that serves a single purpose. If you break it down further than that just to fit it on a screen, you are doing a disservice to those that follow you. The GOAL is to make the programs easy to read. Not to make routines short. Always keep that in mind, and you'll do fine.
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.
midrange.com
