Andy,

> Just a following followup - I looked ath changes in rev 21619 and noticed
> that the troublesome warning flags are still in the "cage"  settings for
> the default. Should they be moved to a v3.4 section also for the cage
> cleaners?

I don't think it's worth it atm (unless you want to join the cage
cleaners!  ;-) ) as I've added a whole lot of new code to autodetect
the warnings flags that the compiler can handle, so such errors that
you detected should hopefully not happen in future.  Well spotted
though :-)

Best regards,

Paul

Reply via email to