Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
X-T2-Posting-ID:	dCnToGxhL58ot4EWY8b+QGwMembwLoz1X2yB7MdtIiA=
Date:	Fri, 26 Aug 2005 00:43:50 +0200
From:	Samuel Thibault <samuel DOT thibault AT ens-lyon DOT org>
To:	cygwin AT cygwin DOT com
Cc:	dave AT mielke DOT cc
Subject:	perennity of cygwin_internal(CW_GET_ERRNO_FROM_WINERROR,err)
Message-ID:	<20050825224350.GT7662@bouh.ens-lyon.fr>
Mail-Followup-To:	Samuel Thibault <samuel DOT thibault AT ens-lyon DOT org>, cygwin AT cygwin DOT com, dave AT mielke DOT cc
Mime-Version:	1.0
User-Agent:	Mutt/1.5.9i-nntp

Hi,

While writing a library for instance, we'd like
to return appropriate errno values, and for this
cygwin_internal(CW_GET_ERRNO_FROM_WINERROR,err) would be much useful.

Documentation says "Stay away unless you know what you're doing". Could
it be removed some day, and hence we shouldn't use it?

Regards,
Samuel

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -