I have not found something for "comparison of unsigned > expression < 0 is always false" when a template type is unsigned > (http://gcc.gnu.org/ml/gcc-help/2010-08/msg00284.html). -Wno-type-limits. But it might be throwing the baby out with the bath water (http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11856).
On Aug 29, 9:50 pm, Jeffrey Walton <[email protected]> wrote: > -Wno-unused-parameter and -Wno-unused-variable should help. > > I've moved to using -Wall -Wextra -Wno-deprecated -Wno-unused to get > all warnings (don't let -Wall fool you) while cutting down on most > noise. I have not found something for "comparison of unsigned > expression < 0 is always false" when a template type is unsigned > (http://gcc.gnu.org/ml/gcc-help/2010-08/msg00284.html). > > Jeff > > On Aug 19, 9:53 am, "wolf.lammen" <[email protected]> wrote: > > > I just learned that 'typedef' is not sufficient, as it does not > > complain when the assertion fails. This renders my suggestion invalid. > > > I apologize for any inconvenience. > > > Cheers > > > Wolf Lammen -- You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [email protected]. More information about Crypto++ and this group is available at http://www.cryptopp.com.
