|
On 12/16/05, Fisher, Don <dfisher@xxxxxxxxxxxxx> wrote: > > Watch out for decimal data errors and numeric overflow operations like the > old date conversion trick (DATE1 MULT 100.0001 DATE2). You're probably > safe > from the former, but you might check for the placement of *BLANKS into > numeric fields or data structures with numeric sub-fields. Hmmm. I thought the numeric overflow was only affected if I converted to use EVAL. Will the date conversion trick bomb if I leave it straight from the RPG-III style? Just asking, but we don't have any of those type of date conversions (all dates are converted with data structures - YUCK). I don't think DDEs are an issue. I'll have to check on *BLANKS and numerics. If there was a "MOVE *BLANKS NUMBER" and NUMBER is numeric, will the -IV compiler catch it? Or will run-time act any differently than it did under RPG-III? Generally speaking (and thankfully), the legacy apps here were all fairly well written for their day. I've yet to come across doing funny stuff with blanks and numerics, and have never seen a 100.0001 or 10000.01 kind of multiplication in the code here. I did come across a FREE opcode in the converted app but, fortunately, the app being FREE'd was updated at some point to accept a negative number in a batch number parameter to signal the program to seton LR and get out. Thanks, Dan
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.