On Wed, Feb 4, 2009 at 3:23 PM, Alan Shouls wrote:
> Hi James,
>
>> The NSXML object is probably calling autorelease on something in its
>> dealloc method (this is perfectly legal, and should generally be seen as
>> implementation detail - you're just seeing a side effect of it here).
>
> Right -
Hi James,
The NSXML object is probably calling autorelease on something in its
dealloc method (this is perfectly legal, and should generally be
seen as implementation detail - you're just seeing a side effect of
it here).
Right - thanks for this. This explains what is happening.
Best reg
On 4 Feb 2009, at 18:06, Alan Shouls wrote:
I am using NSXML in a C++ and am working through some test cases and
have
come across something I can't quite figure out. Here is what I do:
1. Create an Auto Release Pool
2. Create an NSXML object using [NSXMLDocument alloc] initWithData:
(NSData
On Feb 4, 2009, at 11:06 AM, Alan Shouls wrote:
I then get a warning NSCFString autoreleased with no pool in place -
just
leaking
If, however I do things so that I release my NSXML object before
releaseing
the Auto Release Pool - no message.
Does anyone have any insight into why this is
Hi
I am having some problems with NSXML and auto relese pools.
I am using NSXML in a C++ and am working through some test cases and have
come across something I can't quite figure out. Here is what I do:
1. Create an Auto Release Pool
2. Create an NSXML object using [NSXMLDocument alloc] initWit
