• 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: Fast Enumeration and temporary objects/autoreleasing
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Fast Enumeration and temporary objects/autoreleasing


  • Subject: Re: Fast Enumeration and temporary objects/autoreleasing
  • From: Patrick Robertson <email@hidden>
  • Date: Tue, 17 Apr 2012 08:11:30 +0100

> While you have had the question answered, the fact you asked it shows a
misunderstanding about memory management.

Next time in my reply I will be clear to state that
a) I have realised my mistake
b) I have learnt from it to
to save you some time writing your response ;-)
I do appreciate your help though.

> When it comes to autorelease pools, we primarily see them as a
performance tuning technique. If your code is not running into performance
problems and if the documentation does not explicitly tell your code to use
a pool (say for use with NSThread), then please don't worry about it.

Really well put, thanks. I also like the C-style syntax, looks much neater.


It looks like once again this question may well turn into a discussion
about memory management... There should be no need really as it's so simple
:P

On 17 April 2012 07:08, Dave Zarzycki <email@hidden> wrote:

> On Apr 17, 2012, at 1:28 AM, Graham Cox <email@hidden> wrote:
>
> > …having been using Objective C productively for over 10 years now, that
> I still find ARC something I have not needed. So far. I'm kinda hoping that
> remains true, because it actually seems pretty complicated in order to
> cover all the arcane use-cases and I'd rather stick to what I know which
> has the overwhelming advantage of being really, really simple.
>
> ARC simply automates and enforces Cocoa conventions. No more, no less.
> Therefore those "arcane use-cases" are in fact where programmers get
> themselves into really subtle trouble with manual reference counting.
>
> davez
> _______________________________________________
>
> 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
>
_______________________________________________

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


References: 
 >Fast Enumeration and temporary objects/autoreleasing (From: Patrick Robertson <email@hidden>)
 >Re: Fast Enumeration and temporary objects/autoreleasing (From: Graham Cox <email@hidden>)
 >Re: Fast Enumeration and temporary objects/autoreleasing (From: Dave Zarzycki <email@hidden>)
 >Re: Fast Enumeration and temporary objects/autoreleasing (From: Graham Cox <email@hidden>)
 >Re: Fast Enumeration and temporary objects/autoreleasing (From: Dave Zarzycki <email@hidden>)

  • Prev by Date: Re: Fast Enumeration and temporary objects/autoreleasing
  • Next by Date: Re: Fast Enumeration and temporary objects/autoreleasing
  • Previous by thread: Re: Fast Enumeration and temporary objects/autoreleasing
  • Next by thread: Re: Fast Enumeration and temporary objects/autoreleasing
  • Index(es):
    • Date
    • Thread