|
To reiterate, my own take on the matter is that unless there's something, like recursibility or data abstraction, or portability, to be gained from making code into a subprocedure, it's better off as a subroutine, because there's less overhead involved, and because it can call other subroutines in the main procedure. Moreover, unless there's something, like readability or modularity, to be gained from making code into a subroutine or subprocedure, it's better off inline, because that has the least overhead of all. -- JHHL
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
