X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.1 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <4A82CF78.4050504@comcast.net> Date: Wed, 12 Aug 2009 10:19:36 -0400 From: Larry Adams User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) 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> <20090812141530 DOT GA14016 AT calimero DOT vinschen DOT de> In-Reply-To: <20090812141530.GA14016@calimero.vinschen.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Corinna, It's Solaris 10 :(. They must "set" the standard these days ;) Larry Corinna Vinschen wrote: > 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 > > -- 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