"William A. Rowe, Jr." <[EMAIL PROTECTED]> writes: > Before anyone even _considers_ polluting the API [which would > raise an instant veto from me] we have to finally address the create > time issue on non-Unix. Then we can get such a patch committed > to fit this resolution of this issue.. > > Unix has ctime, mtime and atime. How often will we change all three > at once, or do we want to change a single requested time-at-a-time?
That is a key question. I wish I knew the answer :) Rob, what is your use case by the way? Not that it is the answer for everybody, but I'm curious. The change-one-time per call handles your issues nicely. It might be nice to have a flag that says to just set everything to the one time so that we don't waste a syscall trying to preserve the times we don't think we're supposed to modify. -- Jeff Trawick | [EMAIL PROTECTED] Born in Roswell... married an alien...
