If you don't use the FUSEObjC api (objective-c bindings to MacFUSE) then
this probably won't be interesting.
I've just checked in more changes the FUSEFileManager.{h,cc} that modify the
API so that filesystems can return proper "errno" values for almost all of
the methods. In some cases method names have changed to reflect their
NSFileManager API equivalents. Expect existing code to need some minor
changes in order to compile. I realize this might be a bit annoying, but
I'm positive it is for the best.
The previous code took the approach of choosing a default error value for
the failure case. For example, moveItemAtPath:toPath: would return EACCES
for all failures. If you "man rename", you'll find a number of possible
errors that can be returned from such an operation. Always returning EACCES
on failure will cause the Finder to flip out when it may not have to, so it
is best to spend a little effort and return a proper error value in the
posix domain. The code will still fall-back on the old default error value
if you don't feel like setting a proper NSError, but I encourage you to do
that little bit of extra work.
Comments and complaints are welcome :-)
ted
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"macfuse-devel" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/macfuse-devel?hl=en
-~----------~----~----~----~------~----~------~--~---
