On 08/05/2010, at 10:33 PM, Chris Hird wrote:

I use #Mapinc all the time on V6R1?

Hmm ... that made me stop. My current understanding was that it had gone with VRM510 and that GENCSRC was provided instead. Your comment made me question that understanding. I see the 510 C/C++ Programmer's Guide states:

Note: #pragma mapinc will be phased out in future releases. It is recommended
that you use the GENCSRC utility.

I expect that is the source of my belief. To me that appears to be a statement of direction and intending to remove a useful feature (even if OS/400-specific) is just as bad as actually removing it.

I see the 610 C/C++ Programmer's Guide no longer has this note but does state that mapinc is available only in C and not in C++ (not a big deal in my view since I hate C++ even more than C). Perhaps IBM has changed direction and no longer intends to phase mapinc out?

I note Appendix A. attempts to give the impression that GENCSRC is somehow better than mapinc. Won't convince me. How can a static definition that must be updated whenever the file definition changes be better than having the compiler determine the layout at compile-time?

I did a quick search of the archives and see that I knew it had not yet been dropped at 530 but I honestly don't recall that--I must be getting old.

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

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 here. If you have questions about this, please contact [javascript protected email address].