Simon

I use #Mapinc all the time on V6R1? What compiler are you using?
Sent from my BlackBerry® wireless device

-----Original Message-----
From: Simon Coulter <shc@xxxxxxxxxxxxxxxxx>
Date: Sat, 8 May 2010 11:03:33
To: C programming iSeries / AS400<c400-l@xxxxxxxxxxxx>
Subject: Re: [C400-L] C compiler doesn't


On 08/05/2010, at 9:44 AM, James H. H. Lampert wrote:

Simon Coulter wrote:
I suspect this has little to do with Rochester.

Where else?

Wherever the C compiler comes from now. Compilers in general come from
Toronto--not sure whether C is there since irRational have taken over
all this stuff.


Much in C changed at VRM510--see various complaints from me in the
archives. Different C compiler.

Well, as long as it compiles what we need it to . . .

That's questionable. I ran into a bunch of issues taking complex C
source that compiled on 440 to 510. Gave up initially and used
TGTRLS(V4R4M0).


Many includes stored in stream files.

What stream files, and where?

That's an exercise for you. Start at /QIBM.


Although the new C compiler is more consistent with C on other
platforms it has lost much when compared to the previous C compiler.


Lovely. Please tell me it still has _Ropen, _Rread, and so forth, and
packed decimal.

Yes, but it lost mapinc support--got a stupid alternative command to
create an include from the file description instead.

Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------




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-2019 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].