ANN: wxWidgets 2.7.1 released

[Vadim Zeitlin]

On Wed, 01 Nov 2006 20:39:30 +0100 Troels <tk at tk.tk> wrote:

T> A few more 2.7.2 'preview' observations:
T> 
T> - samples/mfc: doesn't link (all builds)
T> Remedy: Not Using MFC -> Use MFC in a Shared DLL, all builds

 I don't know what does this option does but if it just links with MFC
libraries, it should be possible to just put some #pragma comment(lib) in
the sample itself.

T> - samples/mfc: hangs on exit
T> (seen with Win32 Debug + Win32 DLL Debug builds, wxUSE_MFC=0)

 Hmm, is this a regression?

T> - samples/mfc: lots of leaks (no new issue, bug #1554728)
T> (Win32 DLL Debug build only,START_WITH_MFC_WINDOW=1,wxUSE_MFC=0/1)

 Are these real leaks or just the reports from wx?

T> - Scary warnings, probably found and fixed already:
T> 
T> wx\src\common\bmpbase.cpp(31) : warning C4003: not enough actual 
T> parameters for macro 'IMPLEMENT_VARIANT_OBJECT_EXPORTED_NO_EQ'
T> wx\src\common\bmpbase.cpp(32) : warning C4003: not enough actual 
T> parameters for macro 'IMPLEMENT_VARIANT_OBJECT_EXPORTED_NO_EQ'
T> wx\src\common\colourcmn.cpp(29) : warning C4003: not enough actual 
T> parameters for macro 'IMPLEMENT_VARIANT_OBJECT_EXPORTED_NO_EQ'
T> wx\src\common\image.cpp(52) : warning C4003: not enough actual 
T> parameters for macro 'IMPLEMENT_VARIANT_OBJECT_EXPORTED_NO_EQ'

 Actually it doesn't look like they're fixed and I wonder why I don't get
these warnings myself. As WXDLLEXPORT is empty/nothing when using static
libraries the macro is indeed lacking its second argument. And while this
happens to be ok in this case, it's still bad practice. But VC7 is silent
about this. Do you use VC6?

 Regards,
VZ

-- 
TT-Solutions: wxWidgets consultancy and technical support
               http://www.tt-solutions.com/