×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




The other thing is that the string handling BIFs are using work fields
anyway.  It's the same idea--hide the implementation. I agree with that
100%--especially if the procedure version helps make the code more readable.


> -----Original Message-----
> From: Douglas Handy [mailto:dhandy1@bellsouth.net]
> Sent: Tuesday, June 11, 2002 11:56 AM
> To: rpg400-l@midrange.com
> Subject: Re: right$
>
>
> Joel,
>
> >I'm lazy and absent minded so I don't mind the work field
> too much.<g>  ...  In
> >some ways I'd prefer the work field so I could look at the code a
> >week later, read the comment, and understand what I was trying to do.
>
> That's the same reasons I created a Right() function in a
> service program back
> at V3R2, along with lots of other string handling functions.
> It uses work
> variables but who cares?  The code in the calling program
> would look like:
>
>    MYVAR = Right( '   thisisseveralcharacters   ': 10 )
>
> or more likely use a variable name for the first argument.
>
> Why not just create a subprocedure to do it?  And better yet,
> put it in a
> service program?
>
> Doug
> _______________________________________________
> 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.
>


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.