Re: #define bug in gcc for delta builds?
Re: #define bug in gcc for delta builds?
- Subject: Re: #define bug in gcc for delta builds?
- From: Steve Checkoway <email@hidden>
- Date: Wed, 4 Feb 2009 03:23:03 -0800
On Feb 4, 2009, at 2:03 AM, Stephen Northcott wrote:
Since header files get copied verbatim into any file that includes
them (and then preprocessed, of course), my first thought is that
you're including this header from two different source files and
that's causing unexpected behavior. Furthermore, it's possible that
one source file defines _FOO_ and the other does not which could
lead to the data offset issues you mentioned, especially if what
you are conditionally defining is part of a struct or class
definition.
It's actually outside the class definition at the top of the file.
And it's the one and only instance of that header file in the whole
project.
But yes, it is referenced in more than one place.
When you say referenced, do you mean #included?
However to my mind it would be constantly re-defined by that, at
worst.
Actually, that would create multiple externally visible symbols with
the same name and that would cause an error at link time. Since you
are using c++, there was always the possibility that you were
including it inside different namespaces.
Does that shed any more light on it? Am I doing something stupid?
I'm afraid it doesn't for me. If you could reproduce the problem using
a simple test case, that would be handy.
I missed what you said before about cleaning fixing the problem. Ken
Thomases mentioned precompiled headers. That seems like a good place
to look to me too.
--
Steve Checkoway
"Anyone who says that the solution is to educate the users
hasn't ever met an actual user." -- Bruce Schneier
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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