on Mon, 29 May 2006 12:03:56 "Michael D. Crawford" <email@hidden>
wrote:
>>>> On Monday, May 29, 2006, at 06:33AM, Michael D. Crawford <email@hidden>
wrote:
>>> I want to enable faster compiles in a Carbon project without the use of
>>> precompiled headers. That means I can't just #include <Carbon/Carbon.h>
>>> everywhere; I must include only the bare minimum of headers that I need.
>>
>> Syd Polk wrote:
>> Are you using gcc 3.3? I would recommend moving to gcc 3.3, and then using
>> Xcode's builtin PCH mechanism.
>
> I'm afraid that cross-platform application frameworks such as the one I'm
> working on must remain as free as possible from dependencies on particular
> tools. What if some vendor introduces a compiler next year that doesn't
> support precompiled headers? If ZooLib required their use, then it wouldn't
> work with it.
>
> I also specifically don't want ZooLib's users to have to use any particular
> version of any compiler to build ZooLib applications; we make only the most
> basic use of the OS and toolbox calls, so there really should be no reason
> that one couldn't build Mach-O applications on Mac OS X 10.0.
>
> ZooLib still supports Mac OS 9; one doesn't even need Carbon.
Then you may probably just use FlatCarbon headers and write e.g.:
#include <Devices.h>
After all, "what if some vendor introduces a compiler next year
that doesn't support" framework-style includes?
Or forget about fine-graining all-together and don't include
individual headers into individual files, just make a single
include in the project settings (not necessarily precompiled!).
Provided your tool supports this...
Mike
_______________________________________________
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
