|
>>I frankly would have liked to have seen >>a different option on the error >>message; "allow truncation." > >How about: EVAL(T) Hi Mark! I liken numeric truncation to an invalid array index. Rather than add an operand extender to allow the invalid index (or set it to 1) I would prefer to have a hard halt so that the operator is aware that we're about to lose some precision. After consulting with the programmer (me), it would be nice if the operator could take a "T" option, allow truncation and continue. If it's a first test, I might like to see the full scale results because the truncation may be only one of several issues I need to address. But I _prefer_ the hard error. --buck
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.