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



I always get this effect when I forget and create source physical file using simple
CRTSRCPF
and then it takes significant time to recall, that it must be created with explicit CCSID(37) rather than my default 1122...
Another option is to change your user profile CCSID to 37...

PS. You were lucky you had no #include!


-----Original Message-----
From: c400-l-bounces@xxxxxxxxxxxx [mailto:c400-l-bounces@xxxxxxxxxxxx] On Behalf Of drazek_g
Sent: Wednesday, October 10, 2012 7:59 PM
To: c400-l@xxxxxxxxxxxx
Subject: [C400-L] The character } is not a valid C source character

Hi

I have simple c program:
int main(void)
{
return 0;
}

14 - for compilation and error
The character } is not a valid C source character.

It is a CCSID issue.
I have on my profile and source file CCSID=273.

"trigraphs". ??< and ??> works ok.

I tried #pragma convert(273) and also compilation parameter CRTBNDC TGTCCSID(37), but it still doesn't work.
Any Idea?

Regards
Gred Drazek
--
This is the C programming iSeries / AS400 (C400-L) mailing list To post a message email: C400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/c400-l
or email: C400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/c400-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.