• 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: looks like Intel vs. PowerPC difference
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: looks like Intel vs. PowerPC difference


  • Subject: Re: looks like Intel vs. PowerPC difference
  • From: John Stiles <email@hidden>
  • Date: Thu, 3 Aug 2006 13:55:07 -0700

That statement may be true, but I really hope Apple wouldn't do something like that, because in practice it would result in many apps with latent (or not-so-latent) bugs.

On Aug 3, 2006, at 1:49 PM, Bill Bumgarner wrote:

The NSXMLDocument class is free to do whatever it wants to err, including setting it to a completely bogus state, if the xmlDoc was correctly parsed and produced. It might be that the xmlDoc sets the reference pointed to by &err to an allocated instance of NSError that is -release'd upon successful completion, but the reference is not "cleared" because there is no reason to do so.

_______________________________________________ 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
  • Follow-Ups:
    • Re: looks like Intel vs. PowerPC difference
      • From: Kay Roepke <email@hidden>
References: 
 >Re: looks like Intel vs. PowerPC difference (From: Matt Neuburg <email@hidden>)
 >Re: looks like Intel vs. PowerPC difference (From: Bill Bumgarner <email@hidden>)

  • Prev by Date: Re: Pull-down NSPopUpButton with checked item?
  • Next by Date: Programmatically setting Principle Class
  • Previous by thread: Re: looks like Intel vs. PowerPC difference
  • Next by thread: Re: looks like Intel vs. PowerPC difference
  • Index(es):
    • Date
    • Thread