X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: <490A30C8.5000107@sh.cvut.cz> Date: Thu, 30 Oct 2008 23:10:16 +0100 From: Vaclav Haisman User-Agent: Thunderbird 2.0.0.17 (X11/20081017) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: cygwin g++ strictness References: <000201c93ac7$38265930$4001a8c0 AT mycomputer> In-Reply-To: <000201c93ac7$38265930$4001a8c0@mycomputer> OpenPGP: id=63B6B297 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com 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 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 John Emmas wrote: > 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? I think the problem is between keyboard and chair. GCC, no matter how ancient version, just does not do that. That would be in violation of very basic principle of all C and C++ standards. Typedef does not create new types, it merely creates aliases for existing types. > > John - -- VH -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iFYEAREIAAYFAkkKMMgACgkQhQBMvHf/WHmCeQDfcXkerTqBBcqjk8rgPqjSZUJW sRQRkBy8MyLmqQDgl58i+4wWsA0GFerYruZLJyq0A21np0ficI9+Zw== =hRam -----END PGP SIGNATURE----- -- 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/