What does getting the CF stuff by default really hurt?  If someone
doesn't want it then just don't use it.  Making it optional just
complicates things a little.

On the other hand, I guess it just adds more weight to the library if
you know you're not going to use it in the first place.

GC

On Sat, Sep 18, 2010 at 2:11 PM, David Chisnall <[email protected]> wrote:
> On 18 Sep 2010, at 19:06, Quentin Mathé wrote:
>
>> This seems a somewhat cleaner than including CoreFoundation.h in 
>> Foundation.h, but requires to import CoreFoundation.h explicitly when you 
>> depend on it. Not sure what's the best… I'd be tempted to favor Mac OS X 
>> compatibility.
>
>
> Put this in Foundation.h
>
> #ifdef GS_EXCLUDE_COREFOUNDATION_HEADERS
> #import "preface.h"
> #else
> #import <CoreFoundation/CoreFoundation.h>
> #endif
>
> Make -make define this variable and not link to corebase when 
> NO_COREFOUNDATION=yes is defined in a GNUmakefile, other wise don't define it 
> and do link to corebase.  That way, stuff works out of the box for people 
> coming from OS X, but people who don't want the CF stuff can avoid it.
>
> David
> _______________________________________________
> Gnustep-dev mailing list
> [email protected]
> http://lists.gnu.org/mailman/listinfo/gnustep-dev
>



-- 
Gregory Casamento - GNUstep Lead/Principal Consultant, OLC, Inc.
yahoo/skype: greg_casamento, aol: gjcasa
(240)274-9630 (Cell)

_______________________________________________
Gnustep-dev mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnustep-dev

Reply via email to