Re: cygwin g++ strictness

[Vaclav Haisman <v dot haisman at sh dot cvut dot cz>]

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