|
>> 1. As someone already pointed out in this thread, the bifs often don't work exactly the same way as the opcodes. Doing a conversion would usually require some recoding and would always require a lot of testing. >> I think that that would be less of an issue, since most do work the same. >> Actually, most don't work the same. There are little differences. For example - LOOKUP sets %FOUND but %LOOKUP doesn't. - XLATE doesn't change the size of a varying result field but assigning %XLATE to something does, because EVAL does. The one I was going to mention as an exception is LOOKUP. As far as varying fields, I was thinking of "legacy" code, which wouldn't have a VARYING field defined in the pgm, although going from RPG IV fixed to /free would certainly have additional considerations. Come to think of it, would this still be an issue if a VARLEN() field was defined in the DB (but not VARYING)? -mark -mark -------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web.com/ .
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
