From: suhyung Eom <suhyung.eom@samsung.com>
Date: Tue, 31 May 2016 09:09:10 +0000 (+0900)
Subject: [3.0] Change 'char' type to 'signed char'
X-Git-Tag: accepted/tizen/common/20160613.144828~3
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=refs%2Fchanges%2F76%2F72276%2F1;p=platform%2Fcore%2Fuifw%2Fdali-toolkit.git

[3.0] Change 'char' type to 'signed char'

This reverts commit ad070ad5c06fed7558654c544420566e66902b88.
Change-Id: I856f2d3c4c58aa4ffd5db72cc882406e5c4f6e97
---

diff --git a/dali-toolkit/internal/controls/renderers/svg/nanosvg/nanosvgrast.cc b/dali-toolkit/internal/controls/renderers/svg/nanosvg/nanosvgrast.cc
index a3f3bdb..a6c843e 100644
--- a/dali-toolkit/internal/controls/renderers/svg/nanosvg/nanosvgrast.cc
+++ b/dali-toolkit/internal/controls/renderers/svg/nanosvg/nanosvgrast.cc
@@ -878,12 +878,11 @@ static void nsvg__fillScanline(unsigned char* scanline, int len, int x0, int x1,
 // note: this routine clips fills that extend off the edges... ideally this
 // wouldn't happen, but it could happen if the truetype glyph bounding boxes
 // are wrong, or if the user supplies a too-small bitmap
-
- /**
-  * In the original file, using char type (without signed or unsigned) can be interpreted
-  * as 'unsigned char' in some build environments, like ARM architecture.
-  * To prevent the unexpected behavior, we replace 'char fillRule' with 'signed char fillRule' here.
-  */
+/**
+ * In the original file, using char type (without signed or unsigned) can be interpreted
+ * as 'unsigned char' in some build environments, like ARM architecture.
+ * To prevent the unexpected behavior, we replace 'char fillRule' with 'signed char fillRule' here.
+ */
 static void nsvg__fillActiveEdges(unsigned char* scanline, int len, NSVGactiveEdge* e, int maxWeight, int* xmin, int* xmax, signed char fillRule)
 {
     // non-zero winding fill