X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
From:	"Gary R. Van Sickle" <g DOT r DOT vansickle AT worldnet DOT att DOT net>
To:	<cygwin AT cygwin DOT com>
References:	<490A30C8 DOT 5000107 AT sh DOT cvut DOT cz> <001601c93b31$a961b940$4001a8c0 AT mycomputer> <003e01c93b42$e92a17a0$4001a8c0 AT mycomputer> <490AE8A0 DOT 8090009 AT sh DOT cvut DOT cz> <001a01c93b4d$617de150$4001a8c0 AT mycomputer> <490AF1E3 DOT 3020308 AT sh DOT cvut DOT cz> <007401c93b56$ebcfa510$4001a8c0 AT mycomputer> <490B0084 DOT 1070803 AT sh DOT cvut DOT cz> <008a01c93b5a$9338d300$4001a8c0 AT mycomputer> <490B078B DOT 9030007 AT byu DOT net> <20081031135011 DOT GB15518 AT calimero DOT vinschen DOT de> <490B21E9 DOT 80807 AT lysator DOT liu DOT se> <011601c93b6e$49bbb710$4001a8c0 AT mycomputer> <490B268D DOT 3010801 AT byu DOT net>
Subject:	RE: cygwin g++ strictness
Date:	Fri, 31 Oct 2008 23:02:12 -0500
Message-ID:	<AD4006A86F9C4CDA97D99556B68434C9@DFW5RB41>
MIME-Version:	1.0
X-Mailer:	Microsoft Office Outlook 11
In-Reply-To:	<490B268D.3010801@byu.net>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

> From: Eric Blake
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> According to John Emmas on 10/31/2008 9:35 AM:
> > question - when programming like this:-
> > 
> > int32_t i = 32;
> > printf("%d", i);
> > 
> > is it reasonable for a programmer to assume that a type declared as 
> > int32_t will be compatible with "%d" when building for a 
> 32-bit platform?
> 
> It is not portable to platforms with 16-bit int (although 
> these days, such platforms are museumware).

That, or:
- Running your car's engineware.
- Exploding an airbag into your face on detecting a collisionware.
- Recording your vital signsware.
- Pumping insulin into youware.
- Doing your laundyware
- Computerized exercise machinewear
- Microwaveware
- A billion other products with 8- and 16-bit microcontrollers in themware.

CSci doesn't begin and end with the CPU currently on our desks!

>  You can probably 
> ignore the warning on 32-bit platforms, but the better fix is 
> to make your code portable by using <inttypes.h>.
> 

Well, yeah.  There's always the option to not Do The Right Thing(tm), but my
personal experience is that correct way is usually also the easiest way.

-- 
Gary R. Van Sickle


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