libs/newlib-cygwin
libs
/
newlib-cygwin
mirror of git://sourceware.org/git/newlib-cygwin.git
4
0
Fork 0
Code Issues Projects Releases Wiki Activity

* pathnames.sgml (pathnames-win32-api): Try to use a more clear wording.

This commit is contained in:
Corinna Vinschen 2010-08-18 15:28:15 +00:00
parent ce9898da68
commit 6a84234cd2
2 changed files with 8 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
winsup/doc/ChangeLog
View File

@ -1,3 +1,7 @@
2010-08-18 Corinna Vinschen <corinna@vinschen.de>
* pathnames.sgml (pathnames-win32-api): Try to use a more clear wording.
2010-08-13 Corinna Vinschen <corinna@vinschen.de>
* faq-programming.xml (faq.programming.win32-api): Remove simplicity.

6
winsup/doc/pathnames.sgml
View File

@ -373,7 +373,7 @@ pathnames.</para>
<para>When a Cygwin application is started, the Win32 idea of the current
working directory (CWD) is set to an invalid directory. This works around
the problem that the Win32 CWD is locked in a way which restricts POSIX
functionality. However, the side effect is that a call to, say,
functionality. However, the side effect is that a call to, for instance,
<function>CreateFile ("foo", ...);</function> will fail, since the Win32
notion of the CWD is <emphasis>not</emphasis> the same as the Cygwin notion
of the CWD.</para>
@ -386,7 +386,9 @@ you have two choices.</para>
<itemizedlist spacing="compact">
<listitem>
<para>Either you call <function>SetCurrentDirectory</function> before
calling <function>CreateFile</function>.</para>
calling the Win32 function which requires a valid Win32 CWD
(<function>CreateFile</function>, <function>CreateProcess</function>,
etc).</para>
</listitem>
<listitem>
<para>Or you compile your application as native Win32 (mingw) executable,