cygwin g++ strictness

Ralph Hempel
Fri Oct 31 13:23:00 GMT 2008

John Emmas wrote:

> Is there a simple solution to this?

In general, no. Writing portable code is hard and requires
quite a bit of thought and perhaps more importantly, experience.

First, use the strictest possible warning setting on the compiler
and strive for warning free compiles.

Then what I'd probably do is look closely at the offending code
and imagine all the ways that having incompatible types
that are silently converted will break your code.

Then read up on these issues on the many resources out there
on the web to educate yourself on how these problems manifest
themselves and how to solve them.

Sorry, but it's hard work.


Unsubscribe info:
Problem reports:

More information about the Cygwin mailing list