X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Wed, 12 Aug 2009 16:15:30 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Supporting Data Types "ushort_t" and "uchar_t" Message-ID: <20090812141530.GA14016@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <4A82CBB1 DOT 30507 AT comcast DOT net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A82CBB1.30507@comcast.net> User-Agent: Mutt/1.5.19 (2009-02-20) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Aug 12 10:03, 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. Using > "CYGWIN_NT-6.1 BASEMENTBOX 1.5.25(0.156/4/2) 2008-06-12 19:34 i686 > Cygwin". Please point us to a standard which defines them. I don't see them defined anywhere in POSIX.1-2008, nor on any of my Linux machines. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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