comp.lang.idl-pvwave archive: archive » Re: Reentrant API/IDL_KW

Home » Public Forums » archive » Re: Reentrant API/IDL_KW_OFFSETOF() issue

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: Reentrant API/IDL_KW_OFFSETOF() issue [message #38536]

Tue, 16 March 2004 16:59

Rick Towler
Messages: 821
Registered: August 1998

Senior Member

> I'm no Barnaby Jones, but looking at the following from the export.h file
> (5.5-6.0):
>
> #define IDL_KW_OFFSETOF2(s, m) ((void *)(&(((s *)0)->m)))
> #define IDL_KW_V_OFFSETOF2(s, m) ((char *)(&(((s *)0)->m)))
> #define IDL_KW_S_OFFSETOF2(s, m) ((int *)(&(((s *)0)->m)))
>
> #define IDL_KW_OFFSETOF(m) IDL_KW_OFFSETOF2(KW_RESULT, m)
> #define IDL_KW_V_OFFSETOF(m) IDL_KW_V_OFFSETOF2(KW_RESULT, m)
> #define IDL_KW_S_OFFSETOF(m) IDL_KW_S_OFFSETOF2(KW_RESULT, m)
>
>
> The names lead me to believe that IDL_KW_V_OFFSETOF2() would return void
and
> (by default, as it would be the most common use) IDL_KW_OFFSETOF2() would
> return char. But if this were the case I am sure someone would have run
> into this?

Alas, there is no conspiracy here.

A helpful bird pointed out that C will tolerate such void pointers and
convert them but C++ will not. So IDL_KW_V_OFFSETOF() is the macro I should
use in my case.

Many thanks to those knowledgeable lurkers out there!

-Rick

Report message to a moderator

[Message index]

		Re: Reentrant API/IDL_KW_OFFSETOF() issue By: Rick Towler on Tue, 16 March 2004 16:59
		Re: Reentrant API/IDL_KW_OFFSETOF() issue By: Rick Towler on Tue, 16 March 2004 16:07

Previous Topic:	Reentrant API/IDL_KW_OFFSETOF() issue
Next Topic:	Announcing GDL 0.7, now with PLOT command

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Wed Oct 08 14:52:26 PDT 2025

Total time taken to generate the page: 0.00458 seconds