open() giving ENOENT when trying to create files with control chars
Fri Dec 9 00:31:00 GMT 2005
From: Yitzchak Scott-Thoennes <firstname.lastname@example.org>
> Moving on to another "non-portable" problem, I want to create a file
> with a space at the end of the name, but cygwin is stripping spaces.
> Despite the comment in the code, this does seem to be allowed (though
> I suspect it may be via NtCreateFile only, since windows commands
> don't seem to handle filenames with spaces at the end well). I tried
Windows strips trailing spaces and dots (unless the file name
consists only of spaces). You need a managed mount to
preserve those; otherwise "foo ", "foo.", "foo. . . . ", "foo",
and a bunch of other spellings all refer to the same file.
Unlike in the other case (non-portable characters, which POSIX
allows an implementation to reject), the stripping of trailing
'.' from filenames is a violation of POSIX, but since Windows
is the culprit, cygwin cannot avoid it (except with the overhead
of managed mounts).
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
More information about the Cygwin