Tim Wood

Huh. CFRelease(NULL) now does a SIGTRAP and NSExceptionHandler calls back into ObjC from the handler, which isn’t signal-safe. 15415081.

@tjw Goddamn raise-on-NULL CFRelease(). That’s such bullshit.

@wilshipley @tjw NS_INLINE void CFReleaseSafe( CF_RELEASES_ARGUMENT CFTypeRef cf ) { if ( cf == NULL ) return; CFRelease( cf ); }

@fabricetdc @wilshipley Point is I’d prefer a straight up crash rather than some weird -raise.

@tjw Yah, but the CF bitches shouldn’t have done it in the first place, and it wouldn’t be a problem.

@wilshipley @tjw Heh. More than 10 years later and CFRelease( NULL ) can still rile people up.

@gte @tjw SO FUCKING ANNOYING. Also, DO NOT CRASH IF I PASS IN ‘nil’ parameters! COUGHASSHOLESCOUGH.

@wilshipley Don't hold back, what do you *really* think? // @gte @tjw