summaryrefslogtreecommitdiff
path: root/core/fxcrt/fx_string_unittest.cpp
diff options
context:
space:
mode:
authorTom Sepez <tsepez@chromium.org>2018-09-13 17:41:52 +0000
committerChromium commit bot <commit-bot@chromium.org>2018-09-13 17:41:52 +0000
commita5d7ad3aa8feb08a14b5cca173d673054c1ade23 (patch)
tree259f0c17f5b7a2e09f80948f8b5cc8a04fdb7874 /core/fxcrt/fx_string_unittest.cpp
parentaebace3bd14eaf72d43f63d90700cd1b0fa049ca (diff)
downloadpdfium-a5d7ad3aa8feb08a14b5cca173d673054c1ade23.tar.xz
Introduce FX_Number class as a replacement for FX_atonum().
The issue with FX_atonum() is that it doesn't return any information about whether it range-checked its integer values as a signed or unsigned type, even though it knows this as part of its processing. Rather than adding another out parameter to that function, create a class to hold all this information together. This is the first place things went astray while diagnosing bug 882959, in that a large positive value was cast to float as a negative value. Unfortunately, this doesn't affect the related bug, but is a step in the right direction. Change-Id: I0977ec8fccf85e2632a962507bdd30a1cbe6d33c Reviewed-on: https://pdfium-review.googlesource.com/42353 Reviewed-by: Lei Zhang <thestig@chromium.org> Commit-Queue: Tom Sepez <tsepez@chromium.org>
Diffstat (limited to 'core/fxcrt/fx_string_unittest.cpp')
-rw-r--r--core/fxcrt/fx_string_unittest.cpp47
1 files changed, 0 insertions, 47 deletions
diff --git a/core/fxcrt/fx_string_unittest.cpp b/core/fxcrt/fx_string_unittest.cpp
index 60e7f07523..3059de3e5c 100644
--- a/core/fxcrt/fx_string_unittest.cpp
+++ b/core/fxcrt/fx_string_unittest.cpp
@@ -2,56 +2,9 @@
// Use of this source code is governed by a BSD-style license that can be
// found in the LICENSE file.
-#include <limits>
-
#include "core/fxcrt/fx_string.h"
#include "testing/gtest/include/gtest/gtest.h"
-TEST(fxstring, FX_atonum) {
- int i;
- EXPECT_TRUE(FX_atonum("10", &i));
- EXPECT_EQ(10, i);
-
- EXPECT_TRUE(FX_atonum("-10", &i));
- EXPECT_EQ(-10, i);
-
- EXPECT_TRUE(FX_atonum("+10", &i));
- EXPECT_EQ(10, i);
-
- EXPECT_TRUE(FX_atonum("-2147483648", &i));
- EXPECT_EQ(std::numeric_limits<int>::min(), i);
-
- EXPECT_TRUE(FX_atonum("2147483647", &i));
- EXPECT_EQ(2147483647, i);
-
- // Value overflows.
- EXPECT_TRUE(FX_atonum("-2147483649", &i));
- EXPECT_EQ(0, i);
-
- // Value overflows.
- EXPECT_TRUE(FX_atonum("+2147483648", &i));
- EXPECT_EQ(0, i);
-
- // Value overflows.
- EXPECT_TRUE(FX_atonum("4223423494965252", &i));
- EXPECT_EQ(0, i);
-
- // No explicit sign will allow the number to go negative. This is for things
- // like the encryption Permissions flag (Table 3.20 PDF 1.7 spec)
- EXPECT_TRUE(FX_atonum("4294965252", &i));
- EXPECT_EQ(-2044, i);
-
- EXPECT_TRUE(FX_atonum("-4294965252", &i));
- EXPECT_EQ(0, i);
-
- EXPECT_TRUE(FX_atonum("+4294965252", &i));
- EXPECT_EQ(0, i);
-
- float f;
- EXPECT_FALSE(FX_atonum("3.24", &f));
- EXPECT_FLOAT_EQ(3.24f, f);
-}
-
TEST(fxstring, FX_UTF8Encode) {
EXPECT_EQ("", FX_UTF8Encode(WideStringView()));
EXPECT_EQ(