But ... the -fileExistsAtPath: method is supposed to return YES if
the
path specifies a directory.
For me it returns here (on windows) NO if it is a directory and not a
file...
So, if it's returning NO, there is a bug in the -fileExistsAtPath:
implementation rather than a bug
in respect of whether it is used or -fileExistsAtPath:isDirectory: is
used.
It would also be a way to fix it...
In fact, since -fileExistsAtPath: is implemented as a call to
-fileExistsAtPath:isDirectory:, I can't
see how your patch can possibly fix any problem there might be.
In my patch I call
[fm fileExistsAtPath: path isDirectory:&isDir]
for files the method returns NO and isDir is also NO. For directories
the
method returns NO and isDir is set to YES.