Closed Bug 720941 Opened 9 years ago Closed 9 years ago
_COMPARE and content's equivalent DOUBLE _COMPARE
The implementation clearly indicates it was originally intended to work around some sort of Windows-only bug when it landed in 2004. Whatever problem was being worked around also existed in 2006, when content/xslt/public/txDouble.h picked up a similar implementation. Six or eight years later, we don't even support anything before MSVC 2008 (obviously well after 2006), and tinderbox indicates it's no longer an issue (note that this is even the case with PGO builds, specifically enabled for the push). https://tbpl.mozilla.org/?tree=Try&rev=f7cd9da8b89d Let's get rid of these unnecessary, obfuscatory macros.
Attachment #591373 - Flags: review?(dmandelin)
> Six or eight years later, we don't even support anything before MSVC 2008 Tinderbox uses MSVC 2005. But I'll believe we used something even older back in 2006... ;)
(In reply to Jeff Walden (remove +bmo to email) from comment #0) > Let's get rid of these unnecessary, obfuscatory macros. Yes, let's. Especially if no rationale is given next to the macro definition: we either have to keep a weird thing forever that hardly any other software seems to need, or we can cut it out (and add it back in actually knowing why we need it on the off chance we actually do).
Attachment #591373 - Flags: review?(dmandelin) → review+
Oh, right, MSVC 2008 != 8. Stupid non-version version numbers. https://hg.mozilla.org/integration/mozilla-inbound/rev/c1321dc798b7
Target Milestone: --- → mozilla12
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.