Re: Re: [SOLVED] createDirectoryAtPath anomaly between system versions?
Re: Re: [SOLVED] createDirectoryAtPath anomaly between system versions?
- Subject: Re: Re: [SOLVED] createDirectoryAtPath anomaly between system versions?
- From: "Michael Ash" <email@hidden>
- Date: Fri, 7 Jul 2006 13:28:02 -0400
On 7/7/06, Antonio Nunes <email@hidden> wrote:
I could imagine that isDir would be undefined if the file didn't
exist in the first place (exists == NO), although the documentation
implies otherwise, but that would still not explain how it
consistently holds the correct value (0 which equals NO ) in one
build configuration and consistently holds an incorrect value (64
which equals YES) in another build configuration upon return from the
fileExistsAtPath method when the file doesn't exist.
So my question remains: is this a bug or is there something going on
that I should know about?
Relying on the value of an uninitialized variable will do that. If
it's uninitialized then it will just contain whatever happened to be
lying around in memory. It is extremely common in this situation to
have a bug which only occurs intermittently, or only under certain
circumstances, certain settings, etc.
That said, the documentation implies that this value will always be
set. If indeed it is not (and it sounds like it is not, I would expect
it to return 0 or 1, not 64) then I would file a bug either on the
method or on the docs.
Mike
_______________________________________________
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