FROM : Jakob Olesen
DATE : Thu Aug 03 23:52:20 2006
On 03/08/2006, at 22.49, 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.
In fact, NSXMLDocument does something like this. If it generates /
warnings/ during the parse, err points to an NSError with the
warnings, but it still returns a valid document.
It is not really clear from the docs if I can use this NSError in
that case.
DATE : Thu Aug 03 23:52:20 2006
On 03/08/2006, at 22.49, 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.
In fact, NSXMLDocument does something like this. If it generates /
warnings/ during the parse, err points to an NSError with the
warnings, but it still returns a valid document.
It is not really clear from the docs if I can use this NSError in
that case.






Cocoa mail archive

