X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS
X-Spam-Check-By:	sourceware.org
Message-ID:	<4A82D237.8090006@gmail.com>
Date:	Wed, 12 Aug 2009 15:31:19 +0100
From:	Dave Korn <dave DOT korn DOT cygwin AT googlemail DOT com>
User-Agent:	Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Supporting Data Types "ushort_t" and "uchar_t"
References:	<4A82CBB1 DOT 30507 AT comcast DOT net>
In-Reply-To:	<4A82CBB1.30507@comcast.net>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
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

Larry Adams wrote:
> Hi list,
> 
> Are there plans to support these two data types in the near future.  I
> just ran across this portability issue a few minutes ago.

  They're not part of the C standard.  Are they some definition from the linux
kernel or something?

  POSIX would certainly permit us to add these definitions as an extension(*) so
there shouldn't be any problem if you wanted to submit a patch to newlib (where
Cygwin's types.h comes from).

    cheers,
      DaveK

-- 
(*) - B.2.12 http://www.opengroup.org/onlinepubs/009695399/xrat/xsh_chap02.html

--
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

- Raw text -