FROM : John Stiles
DATE : Thu Aug 03 22:55:07 2006
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.
DATE : Thu Aug 03 22:55:07 2006
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.






Cocoa mail archive

