On 9 May 2007, at 17:53, Xavier Glattard wrote:
Riccardo <multix <at> ngi.it> writes:
#define _NSANIMATION_LOCK \
BOOL __gs_isLocked = NO; \
if (_isThreaded) \
{ \
__gs_isLocked = YES; \
NSDebugFLLog( <at> "NSAnimationLock",\
<at> "% <at> LOCK % <at> ",self,[NSThread
currentThread]);\
[_isAnimatingLock lock]; \
}
it causes a hidden "c99-ism" everywhere. If the definition of
I wrote this stuff, so i guess i could help ;-)
I dont know if this can be avoided :
This is coming from a position of not having been tested nor even
thought through properly, but how about:
#define _NSANIMATION_LOCK \
{ BOOL __gs_isLocked = NO; \
//... \
}
? That should remove the C99-esque behaviour - I don't _think_ it
makes the macro any less usable than it already was but as I say, I
haven't studied its use much.
Graham.
_______________________________________________
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev
