X-Recipient: archive-cygwin@delorie.com
X-Spam-Check-By: sourceware.org
X-Trace: 96890058/mk-filter-4.mail.uk.tiscali.com/B2C/$b2c-THROTTLED-DYNAMIC/b2c-CUSTOMER-DYNAMIC-IP/79.66.2.206/None/johne53@tiscali.co.uk
X-SBRS: None
X-RemoteIP: 79.66.2.206
X-IP-MAIL-FROM: johne53@tiscali.co.uk
X-MUA: Microsoft Outlook Express 6.00.2900.2180Produced By Microsoft MimeOLE  V6.00.2900.2180
X-IP-BHB: Once
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqQEALupCUlPQgLO/2dsb2JhbACEG1TILINR
X-IronPort-AV: E=Sophos;i="4.33,517,1220223600";     d="scan'208";a="96890058"
Message-ID: <000201c93ac7$38265930$4001a8c0@mycomputer>
From: "John Emmas" <johne53@tiscali.co.uk>
To: <cygwin@cygwin.com>
Subject: cygwin g++ strictness
Date: Thu, 30 Oct 2008 19:35:37 -0000
MIME-Version: 1.0
Content-Type: text/plain; 	format=flowed; 	charset="Windows-1252"; 	reply-type=original
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

When compiling things under cygwin I'm noticing that the compiler is very
strict about things like typedef'd variables.  For example if 'gint' is
typedef'd as int and 'int32' is also typedef'd as int I can't pass an int32
to a function that requires gint.  This means I'm having to put dozens of
casts all over the place.  Is there any way to avoid this?  e.g. a compiler
switch that would make the compiler a bit more lenient?

John 


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

