RE: Target for numeric operation too small

["Westdorp, Tom" <Tom.Westdorp@xxxxxxxxxxxxxxxxxx>]

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]
>Toronto added the option to have ADD/SUB/etc. blow up on overflow the way
>that EVAL does.

Option?  Cool!  How do I turn it off?  :-)

-----Original Message-----
From: Jon Paris [mailto:Jon.Paris@Partner400.com]
Sent: Friday, December 07, 2001 8:50 AM
To: rpg400-l@midrange.com
Subject: Target for numeric operation too small


 >> So the compiler /can/ figure out if a field's going to be too small.  So
we get a message in the compiler output, and 99.999% of us will ignore it
anyway.

Seems to me that one possible solution to this issue would be to have a
compiler option that raises the severity of the "too small" warning message
so that it kills the compile.  Of course you'd still have to remember to
specify it .......

Changing the compiler to allow truncation is a definite no-no for me.  I
always thought he way that RPG/400 worked was idiotic and was delighted when
Toronto added the option to have ADD/SUB/etc. blow up on overflow the way
that EVAL does.

Jon Paris
Partner400

_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
or email: RPG400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.