https://svn.boost.org/trac10/ticket/489 <pre class="wiki">Hello, seems since RC1_1_33_0 the amount of warning has increased once more. Compling with gcc 4.02 with "-Wall -pedantic" It's pretty annyoing and floods the output unnecessary. Other parts of boost dont have this problem... ---- snip --- boost/boost/archive/binary_iarchive.hpp:33: warning: 'class boost::archive::binary_iarchive_i mpl&lt;boost::archive::binary_iarchive&gt;' has virtual functions but non-virtual destructor /home/rmichels/minimon/sdk/boost/boost/archive/binary_iarchive.hpp:76: warning: 'class boost::archive::binary_iarchive' has virtual functions but non-virtual destructor boost/boost/archive/detail/common_oarchive.hpp:31: warning: 'class boost::archive::detail::co mmon_oarchive&lt;boost::archive::binary_oarchive&gt;' has virtual functions but non-virtual destructor boost/boost/archive/basic_binary_oarchive.hpp:53: warning: 'class boost::archive::basic_binar y_oarchive&lt;boost::archive::binary_oarchive&gt;' has virtual functions but non-virtual destructor boost/boost/archive/basic_xml_iarchive.hpp:40: warning: 'class boost::archive::basic_xml_iarc hive&lt;boost::archive::xml_iarchive&gt;' has virtual functions but non-virtual destructor boost/boost/archive/xml_iarchive.hpp:39: warning: 'class boost::archive::xml_iarchive_impl&lt;bo ost::archive::xml_iarchive&gt;' has virtual functions but non-virtual destructor -------------------- There are some more ... Whats the purpose of not having virtual dtor but virtual functions? Could you please supply a solution, this stuff clutters output much. Regards, A. Focht </pre> en-us /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/489 Trac 1.4.3 Robert Ramey Wed, 09 Nov 2005 21:16:15 GMT https://svn.boost.org/trac10/ticket/489#comment:1 https://svn.boost.org/trac10/ticket/489#comment:1 <ul> <li><strong>status</strong> <span class="trac-field-old">assigned</span> → <span class="trac-field-new">closed</span> </li> </ul> <pre class="wiki">Logged In: YES user_id=396141 This is only a warning. The code makes base class destructors private so that the most derived class destructors must be explicitly called. This was a change made in the course of addressing issue related to dynamic loading/unloading runtime code which serialized data. To avoid these warnings, the serialization tests suppress it explicitly. In the future, we might or might not tweak the code to avoid the warning even though its innocuous. Robert Ramey </pre> Ticket