Yes, this would fail, as now the document is registered with the
resolved
file name. You either need to resolve the symbolig link before you do
the
documentForFileName: lookup or later in NSDocument
readFromFile:ofType:. But
first you should check the comment in NSDocument
loadFileWrapperRepresentation:ofType:. There somebody stated before
the
exception gets raised:
/*
* This even happens on a symlink. May want to use
* -stringByResolvingAllSymlinksInPath somewhere, but Apple
doesn't.
*/
If this is still true, we should stick with the current behaviour.
Perhaps
somebody with an Apple computer and to much time could try and find
out at
which point Cocoa resolves symbolic links, if they get resolved a t
all.