Re: The target for a numeric operation is too small!!!!!

Jim wrote:
>I've complained in the past about some of the way the Eval
>expression works, but I must say in this case I absolulty agree
>that your program should bomb and not continue.  My biggest
>issue with Eval is when it *doesn't* tell me something may be
>wrong.  The fact is, you are trying to stick ten pounds of stuff
>in a five pound bag, it just ain't gonna happen.

Jim:  There are two situations here.  First, let's look at
potential overflow.  Would you want a diagnostic message
every time you code "EVAL N=N+1"?  That is one of the most
common computation.  If you have to wade through dozens of
messages complaining about the possibility of overflow,
you're just going to ignore the message anyways, and you're
back to square one.

The other source of trouble is where the intermediate
results get so big that the number of decimal places in the
result gets chopped down to zero.  We DO have a warning
message for that.  Every time the number of decimal
positions in an intermediate result gets reduced, we issue
warning message 7551.  If this happens, EXPROPTS(*RESDECPOS)
can often fix the potential for problems.

Cheers!  Hans

Hans Boldt, ILE RPG Development, IBM Toronto Lab, boldt@ca.ibm.com


+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---