Re: time.h vs Time.h
Re: time.h vs Time.h
- Subject: Re: time.h vs Time.h
- From: Massimo Marino <email@hidden>
- Date: Sat, 28 Aug 2004 00:34:14 +0200
On Aug 28, 2004, at 12:23 AM, Finlay Dobbie wrote:
On 27 Aug 2004, at 22:22, Massimo Marino wrote:
Still, Eric, MHO is that including an header with < > should somehow
force the USE_HEADERMAP=0 somehow for those headers in an automatic
way: Local headers, even in headermap, should never take precedence
over system ones.
Actually, this behaviour exists for a reason - I believe it is related
to the building of frameworks (so that framework-style includes will
search headers in the project in precedence for those installed, which
may either not exist or may be out of date).
No doubt there is a reason - and a good one even - but then it should
be limited to the scope of that reason: the building of frameworks and
require an explicit optional setting rather then being the default
behavior.
In my case, the very presence of an header anywhere in the project,
even if no target was using it, nor present in any Header build phase,
nor reached via any Header Search path , was enough to mask the sys
header.
Seems like an exceptional case promoted to default system-wide behavior.
However, I have heard that headermaps are going away at some point in
the future.
If not, it would force having USE_HEADERMAP=NO everywhere.
Massimo
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.