X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <49BC958D.2080306@cwilson.fastmail.fm> References: <49BC958D DOT 2080306 AT cwilson DOT fastmail DOT fm> Date: Sun, 15 Mar 2009 08:32:33 +0000 Message-ID: <416096c60903150132g2f33c3a4od84b1122dcf4e92e@mail.gmail.com> Subject: Re: long unsigned int vs. uint32_t again From: Andy Koppe To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes 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 Chuck wrote: > cygwin's has: > #define PRIu32 "lu" > > and has > typedef unsigned int uint32_t; > > Is it possible that our inttypes.h should be changed, to use "u" for 8, 1= 6, and 32 bits? Yep, I'd say so. >=A0Or is gcc's -Wformat=3D2 in 3.4.4 just too strict here -- and should be= checking > the actual bitwidths of types against the formats, before assuming that > "lu" doesn't match uint32_t? No. "long" and "int" are different types, and ignoring this would just store up trouble for when code is ported to platforms with 64-bit longs. Andy -- 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/