|
John King wrote: > > If the driving force behind the RPG enhancements of the past few years > (procedures, prototypes, long field names, qualified data structures, etc) > is to allow RPG coders to better and more easily write readable and > maintainable code, then why on Earth would anyone want to go back to the > practice of using obscure and obtuse 'shortcut op codes'? > Compare these two, 1. arr1(index1) = arr1(index1) + somethingelse 2. arr1(index1) += somethingelse Say it turns out that arr1 should really be arr2: 1. arr2(index2) = arr2(index1) + somethingelse 2. arr2(index2) = somethingelse The first one has double the opportunities for error. More than double really, because it's unlikely that anyone would get the very first correction to arr2 wrong.
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
