Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(416)

Issues Search
    My Issues | Starred     Open | Closed | All

Side by Side Diff: test/mjsunit/number-tostring.js

Issue 82803005: Make sure files end with exactly one new line and police this in presubmit. (Closed) Base URL: https://v8.googlecode.com/svn/branches/bleeding_edge
Patch Set: retry upload Created 7 years ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch | Annotate | Revision Log
« no previous file with comments | « test/mjsunit/newline-in-string.js ('k') | test/mjsunit/number-tostring-func.js » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
1 // Copyright 2008 the V8 project authors. All rights reserved. 1 // Copyright 2008 the V8 project authors. All rights reserved.
2 // Redistribution and use in source and binary forms, with or without 2 // Redistribution and use in source and binary forms, with or without
3 // modification, are permitted provided that the following conditions are 3 // modification, are permitted provided that the following conditions are
4 // met: 4 // met:
5 // 5 //
6 // * Redistributions of source code must retain the above copyright 6 // * Redistributions of source code must retain the above copyright
7 // notice, this list of conditions and the following disclaimer. 7 // notice, this list of conditions and the following disclaimer.
8 // * Redistributions in binary form must reproduce the above 8 // * Redistributions in binary form must reproduce the above
9 // copyright notice, this list of conditions and the following 9 // copyright notice, this list of conditions and the following
10 // disclaimer in the documentation and/or other materials provided 10 // disclaimer in the documentation and/or other materials provided
(...skipping 317 matching lines...) Expand 10 before | Expand all | Expand 10 after
328 assertEquals("-12", Number(-12.345).toPrecision(2)); 328 assertEquals("-12", Number(-12.345).toPrecision(2));
329 assertEquals("-1.2e+2", Number(-123.45).toPrecision(2)); 329 assertEquals("-1.2e+2", Number(-123.45).toPrecision(2));
330 assertEquals("-1.2e+3", Number(-1234.5).toPrecision(2)); 330 assertEquals("-1.2e+3", Number(-1234.5).toPrecision(2));
331 assertEquals("-1.2e+4", Number(-12345).toPrecision(2)); 331 assertEquals("-1.2e+4", Number(-12345).toPrecision(2));
332 assertEquals("-1.235e+4", Number(-12345.67).toPrecision(4)); 332 assertEquals("-1.235e+4", Number(-12345.67).toPrecision(4));
333 assertEquals("-1.234e+4", Number(-12344.67).toPrecision(4)); 333 assertEquals("-1.234e+4", Number(-12344.67).toPrecision(4));
334 // Test that we round up even when the last digit generated is even. 334 // Test that we round up even when the last digit generated is even.
335 // dtoa does not do this in its original form. 335 // dtoa does not do this in its original form.
336 assertEquals("1.3", 1.25.toPrecision(2), "1.25.toPrecision(2)"); 336 assertEquals("1.3", 1.25.toPrecision(2), "1.25.toPrecision(2)");
337 assertEquals("1.4", 1.35.toPrecision(2), "1.35.toPrecision(2)"); 337 assertEquals("1.4", 1.35.toPrecision(2), "1.35.toPrecision(2)");
338
339
340
OLDNEW
« no previous file with comments | « test/mjsunit/newline-in-string.js ('k') | test/mjsunit/number-tostring-func.js » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698