On Sunday 30 November 2003 03:07, Alexandre Julliard wrote: > It's not invalid on Unix, that's the whole point. If we make them > illegal right away it means you won't be able to access legally named
What do you mean by 'access' here? Being able to read from the file? Write to it? Anything else like copying it or moving it? I just did some tests with Word on CXOffice and it's file dialog allowed me to delete a wildcard file, rename and copy it to a non-wildcard filename, but not open it straight away in Word. I guess you want that to be possible as well? The user expects to be able to save any changes under the same name so writing to such a file should be possible too I guess. > Unix files. While checking for existence first will make no difference > in 99% of the cases, it will do the right thing when a file with a > wildcard exists in the file system, and I think that's worth a little > inconsistency. OK, but it gets complicated. Like Shachar showed earlier in this thread wildcard behaviour is version dependent. A solution to this problem could be to do the work in the error path. But this is not enough since Wine's implementations are stacked. You mentioned DOSFS_GetFullName being used by FindFirstFile. I can imagine other complications. For example, if we don't allow new wildcard files to be created, but allow existing wildcard files to be moved, CreateFile should somehow know by whom it was called, since MoveFile uses CreateFile. I don't see a good solution to these problems at the moment, and I would like to help out if I saw one. Any suggestions? -Hans
