|
> From: Alan E. > > The "structured programming opcodes" are "shorthand" for > repetitive sets of insructions for a programmer's benefit. > In the end, it's all branching to RAM addresses and > registers too. And it's okay to prefer generally avoiding > certain techniques. I agree with this, Alan. I usually don't drag out the old "branch on condition" argument unless the conversation is getting a little pedantic. I'm not completely averse to having syntactical standards in a shop. There's no good reason to use a CAB instruction in RPG anymore, although it had its use back in the day. But I don't like it when people insist that one set of standards is "better" than another. As long as the standards are consistent and allow productive coding, it's hard to argue against any of them. Which is also why I get so miffed when the compiler team decides to make design decisions for our own good. The only thing the compiler team should be doing is making the language as flexible as possible, not deciding how they want me to code. But anyway, I think we've addressed the question. Time to move on. Joe
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.