• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: + initialize docs conflict?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: + initialize docs conflict?


  • Subject: Re: + initialize docs conflict?
  • From: j o a r <email@hidden>
  • Date: Wed, 2 Feb 2005 11:35:12 +0100


On 2005-02-02, at 10.30, Will Mason wrote:

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 agree. Had it been extra data per object instance, and not per class, it might make more of a difference. As it is, I doubt that few (if any) of us have so many classes with an implementation of +initialize that it should matter.


j o a r

Attachment: smime.p7s
Description: S/MIME cryptographic signature

 _______________________________________________
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

References: 
 >Re: + initialize docs conflict? (From: Will Mason <email@hidden>)

  • Prev by Date: Re: + initialize docs conflict?
  • Next by Date: Re: + initialize docs conflict?
  • Previous by thread: Re: + initialize docs conflict?
  • Next by thread: Re: + initialize docs conflict?
  • Index(es):
    • Date
    • Thread