Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CodeWarrior and Framework Style Includes

Part of the reason is that they work in tandem with the "framework search path", where the header location is implicit and in fact has a search order (normal headers, private headers). There are also rules about where certain includes can appear: I believe sub-framework headers are not supposed to be referenced in code that does not belong to the parent framework, for instance (so, you should use the parent Carbon/Carbon.h, and only Carbon/*.h files should be allowed to use NavigationServices/NavigationServices.h, say).

In the more general case, the extra qualifier could minimize the number of places the compiler has to search for headers and disambiguate header names that would otherwise conflict.

I'm curious. I use CW and have never used framework-style includes other
than this one in my prefix file:

   #include <Carbon/Carbon.h>

Works fine and all, but I always wonder what the point is of framework-style
includes. 


_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden

This email sent to email@hidden


Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.