summaryrefslogtreecommitdiff
path: root/LICENSE
diff options
context:
space:
mode:
authorTom Sepez <tsepez@chromium.org>2018-09-13 19:27:08 +0000
committerChromium commit bot <commit-bot@chromium.org>2018-09-13 19:27:08 +0000
commit29e180342e18873babf1c74f7c5c056f90a191b0 (patch)
treea897b644169324f748c00822122d9b7da8271933 /LICENSE
parent5700d9e2eea5813861920995815ac092fd7df973 (diff)
downloadpdfium-29e180342e18873babf1c74f7c5c056f90a191b0.tar.xz
Revert "Introduce FX_Number class as a replacement for FX_atonum()."
This reverts commit a5d7ad3aa8feb08a14b5cca173d673054c1ade23. Reason for revert: Speculative revert to get back before flake. Original change's description: > 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> TBR=thestig@chromium.org,tsepez@chromium.org Change-Id: Ia56270c3daa80408fc2b23eb4384a77f03f45b82 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://pdfium-review.googlesource.com/42392 Reviewed-by: Tom Sepez <tsepez@chromium.org> Commit-Queue: Tom Sepez <tsepez@chromium.org>
Diffstat (limited to 'LICENSE')
0 files changed, 0 insertions, 0 deletions