|
On 8/17/2013 4:59 PM, CRPence wrote:
Often there is great importance in taking care with replacing code inTrue dat, Chuck.
a manner that ensures the new code works /the same/ as the original,
given the same inputs. Sometimes the complexity of prior or later
processing and the requirements is not conspicuous. Just like how
converting the input values to a date might be an assumption-too-far
[*ZERO and *HIVAL most conspicuously], so might be the assumption that
the EdtCde(X) is compatible. The 'unedited form' effected with the
Edit-Code-X will produce character string values that are incompatible
with conversion to decimal via %DEC when the input values are negative.
I did indeed assume positive numbers, and since the case seemed to be
dates I thought I was on pretty safe ground, but you're certainly
correct that negative numbers would fail spectacularly.
:)
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.