RE: %CHAR()

> Date: Mon, 20 Nov 2000 11:10:27 -0800
> From: "Westdorp, Tom" <tom.westdorp@stationcasinos.com>
>
> This certainly seems to be an error to me, and it is the source of a lot
of
> remaining MOVE and/or XLATE statements in otherwise all eval form code.
> This surely does not improve readability to anyone's eye, although it
does
> require some documentation in the form "Do NOT change the following
MOVE(s)
> to Eval's or necessary leading 0's will be lost."
>>
>> - -----Original Message-----
>> From: M. Lazarus [mailto:mlazarus@ttec.com]
>> Sent: Saturday, November 18, 2000 4:10 PM
>>>
>>> Remove the blanks of with %trim
>>>
>>> %trim(%char(xxxxx))
>>> %trim(%editc(xxxxx:yyy))
>>> %trim(%editw(xxxxx:yyyy))
>>  There's no need to do that.  These BIFs do it for you already.

"This certainly seems to be an error to me ..."

Tom, what "this" do you mean?  I don't think you're talking about
%trim since that only deals with leading blanks, not leading zeros.

If you can't find an edit code or edit word to return leading zeros,
you might consider a subprocedure that returns the input value with
leading blanks changed to zeros.  Then you could remove those MOVEL
and XLATE lines, and just code this:

C         eval      x = leadingBlanks (%editc(num : 'N'))

Barbara Morris


+---
| 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
+---