Re: compiler bug??
Re: compiler bug??
- Subject: Re: compiler bug??
- From: "Andy O'Meara" <email@hidden>
- Date: Thu, 08 Sep 2005 09:47:54 -0400
Please define "all hell broke loose".
Andy
On 9/8/05 9:21 AM, "Philip Lukidis" <email@hidden> wrote:
> I'm pretty new to kext development. Recently, I've encountered something
> very strange in one of my classes. Briefly, when I place a member variable
> in a certain position within my class, all hell breaks loose. The member
> variable is placed within an #ifdef #endif block, and the symbol is defined
> with the -D switch. When I removed the #ifdef #endif block, I had no
> problems. When I moved the entire #ifdef #endif block to another location
> within the class, I had no problems. But when I placed the #ifdef #endif
> block right under the public keyword, all hell broke loose.
>
> Changing the optimization level to -O0 had no effect. What are your
> thoughts on this? Is there some sort of fatal overflow into my class
> memory, something else, or is this a compiler bug? Note the following:
>
> #ifdef FIRELOGCORE
> myClass* mPub;
> #else
> void* mPub
> #endif
>
> worked, while
>
> #ifdef FIRELOGCORE
> myClass* mPub;
> #endif
>
> did NOT work when placed under the public keyword. Your thoughts on the
> subject would be appreciated.
>
> thanks,
>
> Philip Lukidis
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Xcode-users mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden