|
Yep, I'm aware of that. Actually the point I was trying to make was to make a distinction between the open()/read()/etc APIs which I think of as "System APIs" and the "fopen()/etc" which I think of as part of the C runtime. I wasn't trying to teach people how to use them, or I'd have given working examples :) On Tue, 14 May 2002, Barbara Morris wrote: > Scott Klement wrote: > > > > fopen() and friends are the C functions for accessing the IFS. Those do > > require QC2LE. > > > > If you do use the C functions to access the IFS, watch out for the > external names of the functions. When a C program is compiled with > *IFSIO, fopen() and friends are actually mapped to other names > (_C_IFS_fopen etc) at compile time. Look at stdio.h, where it includes > ifs.h. ifs.h has some pragma maps that map all the I/O functions to the > new names. > > The RPG version of pragma map is EXTPROC. So you'd code something like > this: > > D fopen PR > /if defined(USE_IFS) > D extproc('_C_IFS_fopen') > /else > D extproc('fopen') > /endif > D parms > > or maybe something like this > > D fopen PR extproc('fopen') > D parms > > D fopen_IFS PR extproc('_C_IFS_fopen') > D parms >
As an Amazon Associate we earn from qualifying purchases.
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.