Consider the following code:
for (var i=0;i<3;i++){ var num = i + 0.50; var output = num + " " + Math.round(num) + " " + num.toFixed(0); alert(output); }
In Opera 9.63 I get:
0.5 1 0
1.5 2 2
2.5 3 2
In FF 3.03 I get:
0.5 1 1
1.5 2 2
2.5 3 3
In IE 7 I get:
0.5 1 0
1.5 2 2
2.5 3 3
Note the bolded results. Why are this inconsistencies present? Does this mean that toFixed(0)
should be avoided? What's the correct way to round a number to the nearest integer?
The "toFixed is not a function" error occurs when the toFixed() method is called on a value that is not a number . To solve the error, either convert the value to a number before calling the toFixed method or only call the method on numbers.
toFixed() returns a string representation of numObj that does not use exponential notation and has exactly digits digits after the decimal place. The number is rounded if necessary, and the fractional part is padded with zeros if necessary so that it has the specified length.
Math. round() - rounds to the nearest integer (if the fraction is 0.5 or greater - rounds up) Math. floor() - rounds down.
The toFixed() method converts a number to a string. The toFixed() method rounds the string to a specified number of decimals.
Edit: To answer your edit, use Math.round
. You could also prototype the Number
object to have it do your bidding if you prefer that syntax.
Number.prototype.round = function() { return Math.round(this); } var num = 3.5; alert(num.round())
I've never used Number.toFixed()
before (mostly because most JS libraries provide a toInt()
method), but judging by your results I would say it would be more consistent to use the Math
methods (round
, floor
, ceil
) then toFixed
if cross-browser consistency is what you are looking for.
To address your two original issues/questions:
The issue here lies in the misconception that these should always give the same result. They are, in fact, governed by different rules. Look at negative numbers, for example. Because Math.round
uses "round half up" as the rule, you will see that Math.round(-1.5)
evaluates to -1
even though Math.round(1.5)
evaluates to 2
.
Number.prototype.toFixed
, on the other hand, uses what is basically equivalent to "round half away from zero" as the rule, according to step 6 of the spec, which essentially says to treat negatives as positive numbers, and then add back the negative sign at the end. Thus, (-1.5).toFixed(0) === "-2"
and (1.5).toFixed(0) === "2"
are true statements in all spec-compliant browsers. Note that these values are strings, not numbers. Note further that both -1.5.toFixed(0)
and -(1.5).toFixed(0)
are === -2
(the number) due to operator precedence.
Most modern browsers—or at least the ones you might be expected to support at the time of this writing except for IE—should all implement the specs correctly. (According to Renee's comment, the toFixed
issue you pointed out in Opera has been fixed, presumably since they started using the same JS engine as Chrome.) It's still worth reiterating that, even if the specs were implemented consistently across all browsers, the behavior defined in the spec, particularly for toFixed
rounding, can still be a bit unintuitive for "mere mortal" JS developers who expect true mathematical accuracy—see Javascript toFixed Not Rounding and this "works as intended" bug that was filed on the V8 JS engine for examples.
In short, these are two different functions with two different return types and two different sets of rules for rounding.
As others have suggested, I would also like to say "use whichever function fits your particular use case" (taking special care to note the peculiarities of toFixed
, especially IE's errant implementation). I would personally lean more towards recommending some explicit combination of Edit: ...though, after going back and reading your clarification, your use case (rounding to a whole number) definitely calls for the aptly-named Math.round/ceil/floor
, again, as others have mentioned.Math.round
function.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With