Re: new warnings with gcc 4
Vadim Zeitlin <[email protected]>
| Newsgroups | gmane.mail.mahogany.devel |
|---|---|
| Message-ID | <[email protected]> |
On Tue, 22 Mar 2005 01:08:11 +0200 (EET) Nerijus Baliunas <[email protected]> wrote: NB> First lots of warnings in c-client: NB> NB> mbx.c:1468: warning: pointer targets in passing argument 1 of 'fatal' differ in signedness NB> mbx.c:1475: warning: pointer targets in passing argument 1 of 'sprintf' differ in signedness If gcc 4 continues to give these warnings, it should have a switch (which we should use) to disable them. There is no way MRC is going to fix this and for once I'm not even sure he's wrong. NB> /usr/local/wxWindows.gtk2.nun/include/wx-2.5/wx/stattext.h:24: warning: NB> inline function 'virtual wxStaticTextBase::~wxStaticTextBase()' used NB> but never defined The others could be less clear but this one is clearly bogus: compiler complains about dtor which it should generate itself. Please report this as a gcc bug, if you care about it being fixed. NB> Then in M: NB> NB> /a/M/M/include/Composer.h:55: warning: 'class Composer' has virtual functions but non-virtual destructor NB> /a/M/M/include/CacheFile.h:28: warning: 'class CacheFile' has virtual functions but non-virtual destructor NB> /a/M/M/include/modules/MCrypt.h:32: warning: 'class MCryptoEngine' has virtual functions but non-virtual destructor These are real warnings, strange that g++ 3 doesn't give them (although it does in other cases). The solution is to add a (empty) virtual dtor. Regards, VZ ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click