Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Serious bug in NSFileManager fileExistsAtPath:?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Serious bug in NSFileManager fileExistsAtPath:?

Subject: Serious bug in NSFileManager fileExistsAtPath:?
From: Stéphane Sudre <email@hidden>
Date: Sat, 21 May 2005 06:50:02 -0700

Which result shall be returned by the NSFileManager fileExistsAtPath: API when the file is 0 bytes?

From what I'm seeing, when a file is 0 bytes long (this is due to the fact that it was a Resource fork archived in a zip archive and then decompressed using OpenUp (or another one)), the result is NO.

This leads to the point where the API is saying NO when the file is really here and displayed both by the Finder and the shell.

lstat is returning ENOENT ( /* No such file or directory */ )

This is happening from 10.2.8 to 10.4.1.

Any idea on why an Unix OS is blind when the file is 0 bytes long.


_______________________________________________
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


Follow-Ups:

Re: Serious bug in NSFileManager fileExistsAtPath:?
From: j o a r <email@hidden>
Re: Serious bug in NSFileManager fileExistsAtPath:?
From: Andy Lee <email@hidden>


Prev by Date:
Re: Exclude files from backup

Next by Date:
Re: if an NSWindow is a drawer,	how can I find the NSDrawer instance?

Previous by thread:
Why does spotlight not index my text content?

Next by thread:
Re: Serious bug in NSFileManager fileExistsAtPath:?

Index(es):

Date
Thread