× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Barbara

and if you follow the same support path for brackets you will get "funny"
code in any other CCSID that 37 since you have to substitute brackets
with whatever local character that has the same binary value as CCSID
37 brackets.




On Thu, Oct 10, 2013 at 7:28 PM, Barbara Morris <bmorris@xxxxxxxxxx> wrote:

On 10/10/2013 12:27 PM, John Yeung wrote:
...
In other words, of the myriad reasons not to add braces to RPG,
character encoding issues are not anywhere near the top of the list.


That's true.

The RPG compiler is a bit odd (ok, it's very odd) in the way it handles
the variant @ # and $ characters for variable names. Rather than support
those glyphs, it supports characters with specific hex values. So for
some source file CCSIDs it supports variable names with Å, § ...

But that doesn't mean it has to handle all variant characters that way.

The weird handling of @ # and $ started with RPG/400, and a possibly
excessive zeal for compatibility with RPG/400 kept that same behaviour
for ILE RPG too.

--
Barbara
--
This is the RPG programming on the IBM i (AS/400 and 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.





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

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.