From: Vadim Zeitlin Date: Mon, 23 Jul 2007 18:00:15 +0000 (+0000) Subject: removed wxUSE_STRUTILS which was left over from the old code version X-Git-Url: https://git.saurik.com/wxWidgets.git/commitdiff_plain/6b65e373042341d2f18bfa748360f5c8b2e20dd1 removed wxUSE_STRUTILS which was left over from the old code version git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@47675 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775 --- diff --git a/src/common/wxprintf.cpp b/src/common/wxprintf.cpp index ee415e8bac..f1b2d3914a 100644 --- a/src/common/wxprintf.cpp +++ b/src/common/wxprintf.cpp @@ -60,23 +60,6 @@ using namespace std ; #if !defined(wxCRT_VsnprintfW) || !defined(wxCRT_VsnprintfA) -// wxUSE_STRUTILS says our wxCRT_VsnprintfW implementation to use or not to -// use wxStrlen and wxStrncpy functions over one-char processing loops. -// -// Some benchmarking revealed that wxUSE_STRUTILS == 1 has the following -// effects: -// -> on Windows: -// when in ANSI mode, this setting does not change almost anything -// when in Unicode mode, it gives ~ 50% of slowdown ! -// -> on Linux: -// both in ANSI and Unicode mode it gives ~ 60% of speedup ! -// -#if defined(WIN32) && wxUSE_UNICODE -#define wxUSE_STRUTILS 0 -#else -#define wxUSE_STRUTILS 1 -#endif - // some limits of our implementation #define wxMAX_SVNPRINTF_ARGUMENTS 64 #define wxMAX_SVNPRINTF_FLAGBUFFER_LEN 32