Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
content-class:	urn:content-classes:message
MIME-Version:	1.0
Subject:	RE: new to-do item
X-MimeOLE:	Produced By Microsoft Exchange V6.0.4417.0
Date:	Tue, 17 Jul 2001 14:45:39 +1000
Message-ID:	<EA18B9FA0FE4194AA2B4CDB91F73C0EF08F126@itdomain002.itdomain.net.au>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic:	new to-do item
Thread-Index:	AcEOeqtvLyC72HB7QEaqQuCR+QSUxAAACInQ
From:	"Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To:	"Fish" <fish AT infidels DOT org>, <cygwin AT cygwin DOT com>
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id BAA05860

> -----Original Message-----
> From: Fish [mailto:fish AT infidels DOT org]
> Sent: Tuesday, July 17, 2001 2:49 PM
> To: cygwin AT cygwin DOT com
> Subject: RE: new to-do item
> 
> > As I said, this is a missing header file or import library
> > issue.  The header files and libraries come with the
> > cygwin distribution but they are not related to the Cygwin
> > DLL.
> 
> I think I now see the source of my original confusion. Cygwin 
> DLL code must
> obviously make certain Win32 API calls (in order to emulate 
> the *ix environment)
> and purely as a side effect of that, it allows one to write 
> code that makes the
> same API calls.

Nope. Wrong again.

Some terms - 
the cygwin dll - a dll that exposes a subset of the common unix API
calls.
Cygwin-the-distribution - a compiler,linker,many utilities and the
cygwin dll
 
> But the ability to have one's code be able to make Win32 API 
> calls isn't
> supported per se. It's simply one of the side effects. Is 
> that correct?

Nope. They are orthogonal. You make win32 API calls by linking against a
win32 API exposing dll - say msvcrt.dll or kernel32.dll. That is how you
make those calls _WHETHER OR NOT_ you link against cygwin1.dll.
 
> Thus, as you have now sufficiently explained, my original 
> request to include the
> ability to make a given Win32 API call was inappropriate for 
> the Cygwin DLL TODO
> list. I understand that now.

It's inappropriate for the cygwin dll TODO because it's an orthogonal
issue. It's like reporting a bug with vim on the TODO.

It is _entirely_ appropriate to discuss the missing export for the
open-source w32api package :]
 
Rob

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -