fixed DeleteContents inconsistency: didn't free memory if DeleteContents called befor...

[wxWidgets.git] / include / wx / setup.h

diff --git a/include/wx/setup.h b/include/wx/setup.h
index 0969a450ea73bcd54b32cb3234ffb1e28b5ca67a..de71dae16b4f9d0e0a4a18389146203118a049eb 100644 (file)
--- a/include/wx/setup.h
+++ b/include/wx/setup.h
@@ -16,7 +16,7 @@
 #endif
 
 #ifdef __VMS
-#include "[--]setup.h"
+#include "wx_root:[wxwindows]setup.h"
 #elif defined(__WXMSW__)
 #include "wx/msw/setup.h"
 #elif defined(__WXMAC__)
@@ -33,45 +33,5 @@
 #include "wx/gtk/setup.h"
 #endif
 
-/*
- * Compatibility defines: note that, in general, there is a a reason for not
- * compatible changes, so you should try to avoid defining WXWIN_COMPATIBILITY
- * and do so only if your program really can't be compiled otherwise.
- */
-
-/*
- * Compatibility with 1.66 API.
- * Level 0: no backward compatibility, all new features
- * Level 1: wxDC, OnSize (etc.) compatibility, but
- * some new features such as event tables
- */
-#define WXWIN_COMPATIBILITY 0
-
-/*
- * wxWindows 2.0 API compatibility. Possible values are:
- * 0:   no backwards compatibility
- * 1:   some backwards compatibility, but if it conflicts with the new
- *      features, use the new code, not the old one
- * 2:   maximum backwards compatiblity: even if compatibility can only be
- *      achieved by disabling new features, do it.
- */
-#define WXWIN_COMPATIBILITY_2 1
-
-/*
- * wxWindows 2.0 uses long for wxPoint/wxRect/wxSize member fields and wxDC
- * method arguments, wxWindows 2.1 and later uses wxCoord typedef which is
- * usually int. Using long leads to (justified) warnings about long to int
- * conversions from some compilers and is, generally speaking, unneeded.
- */
-#define wxUSE_COMPATIBLE_COORD_TYPES 0
-
-/*
- * Maximum compatibility with 2.0 API
- */
-#if WXWIN_COMPATIBILITY_2 == 2
-#undef wxUSE_COMPATIBLE_COORD_TYPES
-#define wxUSE_COMPATIBLE_COORD_TYPES 1
-#endif /* WXWIN_COMPATIBILITY_2_MAX */
-
 #endif
        /* _WX_SETUP_H_BASE_ */