• 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: reason for getting NSFileHandle:writeData exception
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: reason for getting NSFileHandle:writeData exception


  • Subject: Re: reason for getting NSFileHandle:writeData exception
  • From: Kevin Kuehl <email@hidden>
  • Date: Tue, 10 Jul 2007 14:10:03 -0700 (PDT)

--- Chris Heimark <email@hidden> wrote:

> Thanks Brian, Kevin and Andrew.
>
> I appreciate your rundown on this behavior. This
> memory model is
> convenient to those who understand it and a surprise
> to those of us
> just getting into Cocoa/ObjC.

You're welcome.  Memory management has been the
hardest part of Cocoa/ObjC for me.  I'm used to using
either malloc/free or letting garbage collection take
care of it.  Unfortunately Apple's documentation here
hasn't helped me all that much and I think it could be
written a lot better.

Kevin Kuehl
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:
    • runtime execution path for NSTask
      • From: Chris Heimark <email@hidden>
References: 
 >Re: reason for getting NSFileHandle:writeData exception (From: Chris Heimark <email@hidden>)

  • Prev by Date: Search Kit on 10.4 and searching in Japanese
  • Next by Date: NSMenu + setSubmenu
  • Previous by thread: Re: reason for getting NSFileHandle:writeData exception
  • Next by thread: runtime execution path for NSTask
  • Index(es):
    • Date
    • Thread