|
Bob wrote: >... >But what would be on my wish list, is to enhance the %TRIMx() built-in >functions to support a second parameter. The second parameter would be a >list of characters that are to be "trimmed" off the field's value. >Today, only blanks are trimmed, it would be nice to be able to trim of >any characters. And that second parameter should support a literal value >or a field name containing the characters to be trimmed. That suggestion was included in the last RPG enhancement survey. Although it received a lot of votes, it wasn't enough to be included in the release currently under development. The item will certainly still be there when (or if) we issue another survey. In the meantime, you can always write your own procedure if this is the kind of thing you do a lot. Just do a %CHECK at the beginning of the string, a %CHECKR at the end, and return the %SUBST of what's in between. I like the idea that the 2nd parameter should be a list of characters to be trimmed off. The description of the item in the last survey suggested that only one character could be specified. Cheers! Hans Hans Boldt, ILE RPG Development, IBM Toronto Lab, boldt@ca.ibm.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.