Am Montag, den 27.07.2009, 11:39 +0800 schrieb Georg Fleischmann:
Hi,
#ifndef MAC_OS_X_VERSION_10_5
- (BOOL) boolValue
{
...
}
#endif
Well that version will work for the current version but will
compile it
again for future versions. My best bet would be something like
Hey,
Am Sonntag, den 26.07.2009, 11:10 +0800 schrieb Georg Fleischmann:
I believe this is not correct. -boolValue is documented in Cocoa
to do
pretty much what the compatibility implementation does. So I believe
the correct fix would be to simply remove our compatibility
category.
Hi,
#ifndef MAC_OS_X_VERSION_10_5
- (BOOL) boolValue
{
...
}
#endif
Well that version will work for the current version but will
compile it
again for future versions. My best bet would be something like the
attached patch. Richard, is this usage of the API macros legitimate?
From my
Hi,
I believe this is not correct. -boolValue is documented in Cocoa
to do
pretty much what the compatibility implementation does. So I believe
the correct fix would be to simply remove our compatibility
category.
[NSString boolValue] has just been added in Mac OS 10.5, but
basically
Hello Georg,
Am Freitag, den 17.07.2009, 10:50 +0800 schrieb Georg Fleischmann:
here is a patch for Base to make GDL2 on Cocoa work with boolean
values from EOModels.
The boolean values in my EOModel files are stored as Y only, not a
complete Yes ( allowsNull = Y; ).
This (Y) works fine
here is a patch for Base to make GDL2 on Cocoa work with boolean
values from EOModels.
The boolean values in my EOModel files are stored as Y only, not a
complete Yes ( allowsNull = Y; ).
This (Y) works fine on a complete GNUstep system, but fails with
the Compatibility code that is only
