|
...are "buffer overruns", which are perhaps the laziest programming mistake any programmer can make...
While perhaps a lazy mistake, they happen all the time, even on iSeries. There have been several cases on this list alone where people have said they have programA calling programB and they're passing field1 as a parm, however when they return from the call field2 is changed, and it's not a parm! It's always tracked down to an issue of programA defining field1 as a 30-char field, but programB defining field1 as a 40-char field. That, is a buffer overrun. NB: I am _not_ saying that the result can be the same as on Windows. Yes, the clear delineation of code and data on iSeries prevents a data-change to a code page, but the lazy mistake happens all over the place, and in many cases is really hard to prevent. -Walden
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.