Re: conversion to ILE

If you wanted to improve upon your idea for a caps routine, I've got
a suggestion for you...

pass the length of the string (or use an operational descriptior)
so you don't have to go through all 32,000 positions.

Then, instead of using the XLATE operation code loop through the
length of the string, get the EBCDIC char code of each character and
determine from that if its a lowercase letter.  if so, use BITON to
turn on bit 1, this will make it uppercase.

This way you (1) only check the part of the string thats necessary,
and (2) the system doesnt have to scan for each character in your
xlate string.  This SHOULD (in theory) improve performance]

Of course, I haven't tried this, but I thought I'd throw the idea
your way, since you were talking about it :)


Rob Berendt <rob@dekko.com> wrote:
> Be careful about generic string handling routines.  They can be a re
>  performance
> killer.  I tried making a 'caps' procedure.  The procedure supported
>  strings up to
> 32,702.  It used the xlate function to do it.  You could do the
>  following:
> eval field = caps('abc')
> However that took a LONG time to run because it had to check all
>  32,702 characters.
> Better to do the xlate function in your own program.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the RPG/400 Discussion Mailing List!  To submit a new         *
* message, send your mail to "RPG400-L@midrange.com".  To unsubscribe   *
* from this list send email to MAJORDOMO@midrange.com and specify       *
* 'unsubscribe RPG400-L' in the body of your message.  Questions should *
* be directed to the list owner / operator: david@midrange.com          *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *