Re: My dilemma with VARYING was ->RE: Error in %trim BIF with V5R3?

Can you make use of the 'trim on passing' option (option(*TRIM) on the 
parameter definition)?  I think it started with V5R3.

rpg400-l-bounces@xxxxxxxxxxxx wrote on 05/06/2006 07:57:00 AM:

CatPath += ('cat=' + %char(CatArr(i)) + '&');

I like using this syntax along with VARYING fields (for all of the 

obvious

reasons), but the thing I struggle with is when I need to be ensured 

that

something does not have trailing blanks (e.g. concatenating a IFS stream
file path). This seems to be the case more often than not.  A lot 

(nearly

all) of my development is done with RPG ILE service program sub procs. 

So I

am constantly providing interfaces to other programmers.  I am not so
worried about them implementing the interface correct (i.e. using 

VARYING in

their programs), but more so that they aren't ensuring the absence of 

blanks

in strings before they pass them on to sub procs I create. Sure I could 

just

insert a few more %TRIM's here and there to bullet proof my programs, 

but

then I just lost some of the benefit I was trying to gain.



Just wondering what other's thoughts are on this matter.

Aaron Bartell

-- 
This is the RPG programming on the AS400 / 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.

#####################################################################################
Attention:
The above message and/or attachment(s) is private and confidential and is 
intended 
only for the people for which it is addressed. If you are not named in the 
address 
fields, ignore the contents and delete all the material. Thank you. Have a nice 
day.

For more information on email virus scanning, security and content
management, please contact administrator@xxxxxxxxxxxx
#####################################################################################