Re: truncating a decimal value in /Free

Ken,
Although I agree that in most occasions one must avoid truncation in
arithmetic operations, what I really criticize is the fact that sometimes
you cannot replicate a non /FREE op code in /FREE, forcing the programmer
to either to "fall back" to non free syntax (think, for example, of the
SCAN opcode) or to code work arounds in /FREE.

Regards
On Jan 11, 2013 5:05 PM, "Ken Sims" <mdrg8066@xxxxxxxxxxx> wrote:

Hi Luis -

On Fri, 11 Jan 2013 12:50:11 -0430, Luis Rodriguez
<luisro58@xxxxxxxxx> wrote:

I love /FREE, but there are some things that, IMHO, could have been made
more compatible with the "original" RPG. For example, using an additional
extender code (e.g. EVAL(T) ) that replicated the non-FREE behaviour of
Z-ADD would have avoided searching for a somewhat "kludgy" workaround.

There aren't many situations where it is desired to truncate the high
order digits.

For overflow situations where the exact value is not required,
generally the desired behavior is to set the value to the highest
value that the field will hold, as various people recommended.

Though I think that no one who suggested setting the highest value
also suggested setting the lowest value (most negative value) for a
field overflow of a negative number. While a negative number overflow
is generally less common than a positive overflow, it shouldn't be
overlooked.

Ken
Opinions expressed are my own and do not necessarily represent the views
of my employer or anyone in their right mind.
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.