Thanks for everyone's help with this. I'm grateful for how quickly we tracked it down. I think I mentioned earlier that this is someone else's code and would involve me in changing dozens (if not hundreds) of modules. Casting seemed like the best workaround but as I've just found out from Dave, that isn't a safe solution for references.
----- Original Message ----- From: "Eric Blake"
Sent: 31 October 2008 13:26 Subject: Re: cygwin g++ strictness
On the other hand, gcc 4 may already be causing ABI changes, so maybe this would be appropriate as part of the switch to gcc 4 and cygwin 1.7.0?
That's a good suggestion and will hopefully get some consideration. In the meantime this looks like being quite a time-consuming problem to solve.... :-( Cheers, 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/
