On 8/9/2016 2:45 AM, Michel LaBarre wrote:
It could very well be that, as one response to me on this thread alluded, CYGWIN's role is to provide the equivalent of an isolated
> POSIX VM under Windows without the VM.
Having used Cygwin for a long time, maybe 10 or 13 years, i see that CYGWIN is *not* an isolated POSIX environment. It brings POSIX to the OS named "Windows". And i enjoyed its interoperability a lot. Cygwin EXEs can call Windows EXEs and vice versa, they put lots of efforts in supporting Windows style ACLs vs. POSIX ACLs, have Active Directory integration, Translate Windows accounts to POSIX style accounts, whatever. And if you are on the C/C++ level, you have the POSIX API, and when you do a simple #include "Windows.h" you have the Win32 APIL *also*. Both in the same Executable. I used that already. This interoperability makes CYGWIN so beautiful. Herbert -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
