I not sure if this fixes the "Invalid number of character ({) when
these macros are defined" error from cppcheck but the start of a
namespace declaration being inside a #if without it's closing } has to
be wrong.
Andy
From f0146a90f638cac49ef2f6020515adde4da4b1ce Mon Sep 17 00:00:00 2001
From: Andy Holder <andy.m.holder@gmail.com>
Date: Thu, 23 Dec 2010 17:31:49 +0000
Subject: [PATCH] cppcheck: Invalid Character errors fix
There are a number of "Invalid number of character ({) when these
macros are defined" error from cppcheck, I think these are
caused by the start of a namespace
declaration being inside a #if without it's closing }.
---
binfilter/bf_sw/source/core/text/sw_porlay.cxx | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/binfilter/bf_sw/source/core/text/sw_porlay.cxx
b/binfilter/bf_sw/source/core/text/sw_porlay.cxx
index b0e8d3b..3ae98df 100644
--- a/binfilter/bf_sw/source/core/text/sw_porlay.cxx
+++ b/binfilter/bf_sw/source/core/text/sw_porlay.cxx
@@ -56,6 +56,7 @@ using namespace ::com::sun::star::i18n::ScriptType;
#ifdef BIDI
#include <unicode/ubidi.h>
+#endif
namespace binfilter {
/*************************************************************************
@@ -72,7 +73,6 @@ namespace binfilter {
*************************************************************************/
-#endif
/*************************************************************************
--
1.7.3.4
Context
- [Libreoffice] cppcheck: Invalid Character errors fix · Andy Holder
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.