From 6b457882d011d218ab4764e71fc8d5edfb1d8a87 Mon Sep 17 00:00:00 2001 From: Tor Lillqvist Date: Thu, 15 Sep 2011 11:55:35 +0300 Subject: We can't #define _HAS_ITERATOR_DEBUGGING 0 in just some of the source files It seems that _HAS_ITERATOR_DEBUGGING affects the layout of some classes, which of course means horrible breakage if some of the source files are compiled with it, the rest not. http://msdn.microsoft.com/en-us/library/aa985939%28v=vs.80%29.aspx http://connect.microsoft.com/VisualStudio/feedback/details/334315/has-iterator-debugging-0-causes-crash I will just have to fix the code in this handful of source files so that it compiles with _DEBUG defined. If I can be bothered. --- fpicker/source/office/OfficeControlAccess.cxx | 4 ---- 1 file changed, 4 deletions(-) (limited to 'fpicker') diff --git a/fpicker/source/office/OfficeControlAccess.cxx b/fpicker/source/office/OfficeControlAccess.cxx index 8a0f0a18180e..50632bf89d95 100644 --- a/fpicker/source/office/OfficeControlAccess.cxx +++ b/fpicker/source/office/OfficeControlAccess.cxx @@ -26,10 +26,6 @@ * ************************************************************************/ -#ifdef _MSC_VER -#define _HAS_ITERATOR_DEBUGGING 0 -#endif - // MARKER(update_precomp.py): autogen include statement, do not remove #include "precompiled_fpicker.hxx" -- cgit