Re: + initialize docs conflict?
Re: + initialize docs conflict?
- Subject: Re: + initialize docs conflict?
- From: Will Mason <email@hidden>
- Date: Wed, 2 Feb 2005 01:30:28 -0800 (PST)
- Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
Frankly, I don't find the arguments that using the static BOOL occupies
space or that's it's not thread-safe are very compelling at all. Okay,
let's say that a static BOOL occupies 4 bytes in your app. Since we're
all using Objective-C instead of assembly language, does any of us care
about 4 bytes? I doubt it. If we do, then I envy those of us who don't
have anything better to worry about. The thread-safe argument doesn't
really thrill me, either. Is the class method +class really any more
thread-safe than using the static variable? I doubt it. Chances are
that if we all use the type sig_atomic_t for the variable, we'll be
just fine, and even if we use BOOL, we'll more-than-likely be just
fine.
I just don't see any compelling reason to use the recommended (self ==
[MyClass class]) procedure over the static variable procedure at all.
If anyone has a compelling reason, then please tell me. The extra 4
bytes in the app don't really convince me...
Thanks,
Will
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden