|
> But I am running into an ever increasing > number of programmers that ask the basic > question "Why use a sub-procedure when it > does the same thing as a program call?" Do they write sub-programs to do one thing, and one thing well? Do their applications written this way provide acceptable performance and maintainability? Do they write sub-procedures to do one thing and one thing well? Do their applications written this way provide acceptable performance and maintainability? If the answers to all of the above are yes, then the question makes perfect sense. They're already writing very modular, re-usable code that is easy to maintain and runs acceptably. What benefits do they accrue from sub-procedures? (they have already brushed aside use in an expressions.) I guess this is how I would approach this sort of question, although it doesn't sound like I would spend too much time on it. It sounds like they've made their minds up already. --buck
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.