|
Joe, >Doug, it's an opinion, I guess. You base yours on the fact that you >commonly misunderstand the MOVE instruction. Somehow, I always managed to >figure it out. In fact, junior programmers managed to figure it out. No, I never said *I* misunderstood them. In fact, you are the one who got the MOVEL to the %subst() wrong in this example. But I don't fully understand MOVEs without knowing the attributes of the operands. And that is *not* the case with the eval alternative. In that context, it is MOVE which is "hidden or secret", ie arcane, and arcane was the word you chose; not me. >In fact, this entire argument that MOVE is hard to understand is probably >the silliest thing I ever heard. If you came into my office looking for a >job and told me that the MOVE instruction was "confusing" I'd send you >packing. I never said they were confusing or that I didn't understand them. Do I think junior programmers can learn the nuances of MOVE? Sure. They MUST do so. But I don't consider a virtue of RPG that MOVE permits the things it does. But I think it is time to let this thread die. You keep attributing statements to me which I did not make. Doug
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.