• 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: Stack-based C++ class to wrap NSAutoreleasePool
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Stack-based C++ class to wrap NSAutoreleasePool


  • Subject: Re: Stack-based C++ class to wrap NSAutoreleasePool
  • From: Clark Cox <email@hidden>
  • Date: Sat, 14 Nov 2009 09:53:34 -0800

On Wed, Nov 11, 2009 at 9:17 AM, Dan Korn <email@hidden> wrote:
> So, is there any reason why I shouldn't do this?

The one thing to be careful of is exceptions. In 32-bit Mac code,
Obj-C and C++ exceptions are completely unrelated. If an Objective-C
exception is thrown, C++ destructors will *not* be called as the stack
is unwound. Just something to be aware of.

--
Clark S. Cox III
email@hidden
_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Stack-based C++ class to wrap NSAutoreleasePool
      • From: Kyle Sluder <email@hidden>
References: 
 >Stack-based C++ class to wrap NSAutoreleasePool (From: Dan Korn <email@hidden>)

  • Prev by Date: Re: [iPhone] OS 3.0 and @synthesize AND @dynamic for the same property
  • Next by Date: Re: controlTextDidEndEditing and buttons...
  • Previous by thread: Re: Stack-based C++ class to wrap NSAutoreleasePool
  • Next by thread: Re: Stack-based C++ class to wrap NSAutoreleasePool
  • Index(es):
    • Date
    • Thread