throw_exception rev. 44954 -> g++ warnings

SVN rev. 44954 from yesterday introduces new g++ warnings (several g++ versions, incl. 4.1.2 Fedora 8). See below. Would it make sense to add the virtual destructors g++ want's to have? Ralf include_te.cpp: #include <boost/throw_exception.hpp> % svn update -r44953 Updated to revision 44953. % g++ -Wall -c -I$hot/boost include_te.cpp % svn update -r44954 U boost/throw_exception.hpp Updated to revision 44954. % g++ -Wall -c -I$hot/boost include_te.cpp boost/exception/detail/counted_base.hpp:17: warning: 'class boost::exception_detail::counted_base' has virtual functions but non-virtual destructor boost/exception/detail/cloning_base.hpp:19: warning: 'class boost::exception_detail::cloning_base' has virtual functions but non-virtual destructor boost/exception/enable_current_exception.hpp:24: warning: 'class boost::exception_detail::clone_base' has virtual functions but non-virtual destructor boost/exception/exception.hpp:27: warning: 'struct boost::exception_detail::error_info_container' has virtual functions but non-virtual destructor

On 5/1/08, Ralf W. Grosse-Kunstleve <rwgk@yahoo.com> wrote:
SVN rev. 44954 from yesterday introduces new g++ warnings (several g++ versions, incl. 4.1.2 Fedora 8). See below. Would it make sense to add the virtual destructors g++ want's to have?
I don't know, what is the official Boost policy on this annoying warning? In my opinion, this warning should be issued only if an attempt to call the non-virtual destructor of a type with virtual functions through a base class pointer is actually made, not simply because the possibility exists. Emil Dotchevski Reverge Studios, Inc. http://www.revergestudios.com/reblog/index.php?n=ReCode
participants (2)
-
Emil Dotchevski
-
Ralf W. Grosse-Kunstleve