|
>I dunno, Buck. If I followed the one proc/one page rule, I'd >have hundreds of procs for a given application, each having >logic that wouldn't be used anywhere else. Yes. This is about all I can say without pushing the limits: Machine code = tedious and error prone. Much repetition required to do the most mundane tasks. Macro assembler = macros capture many mundane tasks and abstract out common functionality. Mainline code still voluminous. RPG = opcodes abstract higher-order functions that macros & many assembler opcodes used to do. Mainlines assemble many opcodes to perform business functions. Procs = abstract even higher-order functions (business level) that many opcodes used to do. Mainlines assemble many procs (but fewer than opcodes did) to perform business functions. --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.