• 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: Tracked down the over-release bug
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Tracked down the over-release bug


  • Subject: Re: Tracked down the over-release bug
  • From: Andy Lee <email@hidden>
  • Date: Sun, 12 Jun 2005 18:50:06 -0400

On Jun 12, 2005, at 6:21 PM, Theodore H. Smith wrote:
I'm sure some will tell me that mixing C++ classes with ObjC classes is generally "not nice", but really I have no choice, because the code I am porting uses C++ classes and I must faithfully replicate them. (it's only a few, thankfully!)

Congratulations on tracking the bug down!

Out of curiosity -- was the fix to add a retain in the copy constructor? That would be my guess, since the copy constructor creates a new reference to the Objective-C object. I would think you'd need the retain in order to balance the release in your destructor.

--Andy

_______________________________________________
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: 
 >Tracked down the over-release bug (From: "Theodore H. Smith" <email@hidden>)

  • Prev by Date: Re: how to make an NSWindow unmovable...
  • Next by Date: Re: how to make an NSWindow unmovable...
  • Previous by thread: Tracked down the over-release bug
  • Next by thread: Tableview with checkboxes for bidirectional to-many relationship
  • Index(es):
    • Date
    • Thread