Getting rid of some warnings on gcc?

I've noticed that a bunch of the gcc tests (Mac OS, Linux, Windows) have many, many warnings, and they're all the same:
/mnt/rh73/home/grafik/CVSROOTs/Boost/boost/boost/token_functions.hpp:305: warning: ` typename
boost::tokenizer_detail::get_iterator_category<Iterator>::iterator_category' is implicitly a typename
and
/mnt/rh73/home/grafik/CVSROOTs/Boost/boost/boost/token_functions.hpp:397: warning: ` typename
boost::tokenizer_detail::get_iterator_category<InputIterator>::iterator_category ' is implicitly a typename
So I tried adding "typename" in two spots. In the MacOS testing, it changed 30+ tests from "Warn" to "Pass". Here's the change: diff -r1.23 token_functions.hpp 304c304 < tokenizer_detail::get_iterator_category< ---
typename tokenizer_detail::get_iterator_category<
396c396 < tokenizer_detail::get_iterator_category< ---
typename tokenizer_detail::get_iterator_category<
-- -- Marshall Marshall Clow Idio Software <mailto:marshall@idio.com> Hey! Who messed with my anti-paranoia shot?

At 10:50 AM 2/3/2004, Marshall Clow wrote:
I've noticed that a bunch of the gcc tests (Mac OS, Linux, Windows) have many, many warnings, and they're all the same: ... So I tried adding "typename" in two spots. In the MacOS testing, it changed 30+ tests from "Warn" to "Pass". Here's the change:
diff -r1.23 token_functions.hpp 304c304 < tokenizer_detail::get_iterator_category< ---
typename tokenizer_detail::get_iterator_category<
396c396 < tokenizer_detail::get_iterator_category< ---
typename tokenizer_detail::get_iterator_category<
VC++ 6.0 fails with the added "typename", so it has to be placed in #if ... #endif. But, yes, the change does clear a lot of gcc warnings. The change seems so innocuous I went ahead and committed it to the CVS HEAD. Thanks, --Beman
participants (2)
-
Beman Dawes
-
Marshall Clow