| Re: In case someone has trouble including export.h [message #29035 is a reply to message #29023] |
Tue, 29 January 2002 12:23   |
Vapuser
Messages: 63
Registered: November 1998
|
Member |
|
|
Ruediger Kupper <Ruediger.Kupper@Physik.Uni-Marburg.De> writes:
> Hi!
>
> We just ran into a problem with IDL5.5's export.h file, when
> including it from a c++ source file:
> I tested g++-2.95 and g++-3.0, and both (most annoyingly)
> choked on it, due to the following reason:
>
> The original export.h shipping with IDL 5.5 featured a prototype
> declaration with a variable named "template". This choice of name
> effectively prevents the code from compiling, when included from C++
> code (even when included 'extern "C" {}').
>
> Solution:
> With variable names being arbitrary (all that matters is the type and
> order of arguments for defining a proper prototype), you may feel free
> to rename it, so as not to interfere with the C++ compiling process.
>
>
> The original call was:
>
> extern char *IDL_CDECL IDL_VarMakeTempFromTemplate
> IDL_ARG_PROTO((IDL_VPTR template, int type, IDL_StructDefPtr sdef,
> IDL_VPTR *res, int zero));
>
> P.S.:
> The IDL_ARG_PROTO(...) macro is defined near the beginning of the
> file. It acts as a null-filter, reproducing it's argument. It can be
> used to completely turn off prototypes in this file, for compatibility
> to non-ANSI-compilers. We could have utilised this by #define-ing
> IDL_CC_NOT_ANSI, which also seemed to fix the above mentioned
> problem. But I felt this being much more interfering than simply
> respelling the name.
>
>
> Hope that this may be helpful,
> regards,
> Ruediger.
>
I have to admit, this newsgroup is a never-ending source of
information to me. I'm about to upgrade my OS to IRIX 6.5.13f and I
was just checking to see if there were any implications for me
regarding IDL. And while the problem you discuss isn't specifically
a problem for me (yet, I'm hoping to stay with IDL 5.3 for the
nonce) nevertheless it could be were I forced to upgrade to 5.5,
since I depend rather heavily on several linkimage routines.
So, for your time and consideration in making your post, I'd just
like to say thanks. I've now squirreled it away in case I run into
this later!
whd
--
William Daffer: 818-354-0161: William.Daffer@jpl.nasa.gov
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
