diff options
| author | Corinna Vinschen <corinna@vinschen.de> | 2010-08-13 15:52:13 +0400 |
|---|---|---|
| committer | Corinna Vinschen <corinna@vinschen.de> | 2010-08-13 15:52:13 +0400 |
| commit | a016fed8bae15b01b279288639215e5fc225678a (patch) | |
| tree | aa2d7ce37576362efafbba41a5ea6672958b0f1c /winsup/doc/overview2.sgml | |
| parent | 260b80740ecf07b137aa6a6711d5d56fdd861d44 (diff) | |
* faq-programming.xml (faq.programming.win32-api): Remove simplicity.
Add note and xrefs to User's Guide chapters explaining restrictions
using the Win32 API.
* new-features.sgml (ov-new1.7.6): Add note about Win CWD.
* overview2.sgml (ov-hi-intro): Add note and xrefs about Win32 API
restrictions. Tone down flexibility.
* pathnames.sgml (pathnames-intro): Add xref to pathnames-win32-api
section.
(pathnames-win32-api): New section describing Win32 CWD restriction.
* setup2.sgml (setup-env-ov): New sub-section.
(setup-env-win32): Ditto, describing Win32 environment restriction.
Diffstat (limited to 'winsup/doc/overview2.sgml')
| -rw-r--r-- | winsup/doc/overview2.sgml | 11 |
1 files changed, 7 insertions, 4 deletions
diff --git a/winsup/doc/overview2.sgml b/winsup/doc/overview2.sgml index b0e3635c7..b89799e45 100644 --- a/winsup/doc/overview2.sgml +++ b/winsup/doc/overview2.sgml @@ -55,9 +55,8 @@ an easy way to port many UNIX packages, with only minimal source code changes. </para> <para> -Note that there are some workarounds -that cause Cygwin to behave differently than most UNIX-like operating -systems; these are described in more detail in +Note that there are some workarounds that cause Cygwin to behave differently +than most UNIX-like operating systems; these are described in more detail in <xref linkend="using-effectively"></xref>. </para> <para> @@ -111,11 +110,15 @@ appropriate.</para> <para>Because processes run under the standard Win32 subsystem, they can access both the UNIX compatibility calls provided by Cygwin as well as -any of the Win32 API calls. This gives the programmer complete flexibility in +any of the Win32 API calls. This gives the programmer some flexibility in designing the structure of their program in terms of the APIs used. For example, they could write a Win32-specific GUI using Win32 API calls on top of a UNIX back-end that uses Cygwin.</para> +<note><para>Some restrictions apply for calls to the Win32 API. +For details, see <xref linkend="setup-env-win32"></xref>, +as well as <xref linkend="pathnames-win32-api"></xref>.</para></note> + <para>The native NT API is used mainly for speed, as well as to access NT capabilities which are useful to implement certain POSIX features, but are hidden to the Win32 API. |