|
On Mon, 23 Aug 2004 18:49:13 -0500, Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx> wrote: > If all I am doing is segmenting my code (as I often do in a state-driven > architecture) then there is no reason to add the code. Especially since > they're equally readable. I don't know about the performance; I haven't > written a benchmark yet. I think Joe touched on the guts of the issue here. SubProcedures allow for the kind of variable segmenting, isolation, and re-usability that is necessary in state-less and object-oriented programming. For typical, "state-driven", top-down RPG programming, there is little substantive difference between SR and SubProc(). I see SubProcedures as being a bit more work, since you need the prototypes. -- Tom Jedrzejewicz tomjedrz@xxxxxxxxx
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.