× 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.



On 10/10/2013 10:39 AM, John Yeung wrote:
On Thu, Oct 10, 2013 at 10:20 AM, Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote:
The C language definition (having an ASCII heritage)
uses { and } and there is no problem world-wide because
as Henrik says - the code point is always the same in ASCII.

But Blake's point is that C *does* live in the native i environment.
Complete with source members in QSYS.LIB files, SEU support, the whole
9 yards. No matter what its heritage, it is a full-fledged i
programming language today, and has been for quite a number of years.

So if IBM can do braces in C on the i, why (as a technical issue,
setting aside whether it's a good idea) couldn't they do braces in
RPG?

I didn't realise that the RPG compiler shares the lexer, parser and
tokeniser with the C compiler.

Subsequently the addition of C and subsequently C++ and Java
to IBM's arsenal caused problems with these characters. But it
was too late to change EBCDIC so people have to work round
the problems.

I wouldn't lump Java in with C and C++ here, because Java source
typically lives in IFS stream files, outside of QSYS.LIB.

The fact is, if EBCDIC can be "worked around" with C and C++, there is
no technical reason they couldn't be worked around with RPG.

Technically, the US can send men to the moon and bring them back again.
All it takes is demand, money, people and time.
--buck

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.