Re: NSFileManager vs Non-Packaged application: 0 - 1
Re: NSFileManager vs Non-Packaged application: 0 - 1
- Subject: Re: NSFileManager vs Non-Packaged application: 0 - 1
- From: David Halliday <email@hidden>
- Date: Mon, 07 Mar 2005 07:06:22 -0600
Stephane Sudre wrote:
On 7 mars 05, at 13:19, Bob Ippolito wrote:
Not all executable files are Mach-O or CFM. It could be a shell
script, or a fat Mach-O file (which is 0xcafebabe, IIRC).
The documentation is correct, so is the implementation. The
**underlying operating system** does NOT execute CFM files. They're
treated more like documents that are handled by LaunchCFMApp. If
there is a function to see if the given path is an "application", it
would be in LaunchServices.
OK, so the NSFileManager isExecutableFileAtPath: is really just a
wrapper around lstat and check for "x" flags...
That's about right, for the case of this particular OS. However,
this API is designed to be OS agnostic, so it can be used independent of
how the "underlying operating system" determines executability. (This
even gives Apple the flexibility to change such things within their OS,
if they so choose).
--
David
_______________________________________________
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