open() giving ENOENT when trying to create files with control chars
Mon Dec 12 09:50:00 GMT 2005
On Dec 8 23:50, Brian Dessent wrote:
> Yitzchak Scott-Thoennes wrote:
> > > 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.
> > I attempted to indicate in the message above that I tried it and
> > succeeded in using filenames with spaces on the end (and *different*
> > files named the same except without the spaces). It seems this is
> > *not* an across-the-board Windows limitation.
> This is probably a difference in the win32 API versus the native API.
Correct. In the native API you can create practically every filename
which doesn't use invalid characters. But these filenames are not
compatible with Win32 functions. Since the bulk of Cygwin is still
using the Win32 API, we can't afford to create Win32 incompatible
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat, Inc.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
More information about the Cygwin