RE: XML-INTO & embedded blanks

This has been in production for 2 years. I discovered it when doing some testing with a copy of live data. The users missed it this time, so there's no way to know if they missed others.

XML-SAX is a big pain, so %trim() it is. I just wanted to make sure I wasn't overlooking door #3. Thank you



-----Original Message-----
From: Jon Paris [mailto:jon.paris@xxxxxxxxxxxxxx]
Sent: Monday, July 09, 2018 5:55 PM
To: Rpg400 Rpg400-L <rpg400-l@xxxxxxxxxxxx>
Subject: Re: XML-INTO & embedded blanks

Answering my own query - it is WAD. I have never noticed that although I understand why it is being done.

I've dealt with literally hundreds of people's questions on using XML-INTO and this has never been an issue.

I think an RFE is needed to add a trim option to preserve internal blanks. Biggest issue, and I suspect the reason this is done in the first place, is how to handle other embedded whitespace characters such as carriage return, line-feed, tabs, etc. My feeling is that "real" spaces should be retained and anything else stripped.

As to handling it - I'd just add the none option and preform the trimming yourself. Moving into XML-SAX if you already have this basically working is going to require a lot more effort than simply adding a group of x = %Trim(x) operations.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com