Chromium Code Reviews| OLD | NEW |
|---|---|
| (Empty) | |
| 1 // Copyright 2010 the V8 project authors. All rights reserved. | |
| 2 // Redistribution and use in source and binary forms, with or without | |
| 3 // modification, are permitted provided that the following conditions are | |
| 4 // met: | |
| 5 // | |
| 6 // * Redistributions of source code must retain the above copyright | |
| 7 // notice, this list of conditions and the following disclaimer. | |
| 8 // * Redistributions in binary form must reproduce the above | |
| 9 // copyright notice, this list of conditions and the following | |
| 10 // disclaimer in the documentation and/or other materials provided | |
| 11 // with the distribution. | |
| 12 // * Neither the name of Google Inc. nor the names of its | |
| 13 // contributors may be used to endorse or promote products derived | |
| 14 // from this software without specific prior written permission. | |
| 15 // | |
| 16 // THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS | |
| 17 // "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT | |
| 18 // LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR | |
| 19 // A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT | |
| 20 // OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, | |
| 21 // SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT | |
| 22 // LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, | |
| 23 // DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY | |
| 24 // THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT | |
| 25 // (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE | |
| 26 // OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. | |
| 27 | |
| 28 // Check for parsing of proper ES5 15.9.1.15 (ISO 8601 / RFC 3339) time | |
| 29 // strings that contain millisecond values with exactly 3 digits (as is | |
| 30 // required by the spec format if the string has milliseconds at all) | |
| 31 assertEquals(1290722550521, Date.parse("2010-11-25T22:02:30.521Z")); | |
|
Lasse Reichstein
2010/11/25 12:56:05
Perhaps add some spacing here, before the next com
| |
| 32 // Check for parsing of extension/generalization of the ES5 15.9.1.15 spec | |
| 33 // format where millisecond values have only 1 or 2 digits. | |
| 34 assertEquals(1290722550500, Date.parse("2010-11-25T22:02:30.5Z")); | |
| 35 assertEquals(1290722550520, Date.parse("2010-11-25T22:02:30.52Z")); | |
| 36 assertFalse(Date.parse("2010-11-25T22:02:30.5Z") === Date.parse("2010-11-25T22:0 2:30.005Z")); | |
| 37 // Check that we truncate millisecond values having more than 3 digits | |
| 38 assertEquals(Date.parse("2010-11-25T22:02:30.1006Z"), Date.parse("2010-11-25T22: 02:30.100Z")); | |
|
Lasse Reichstein
2010/11/25 12:56:05
Should this be ".1005Z" (and not ".1006Z")?
| |
| 39 // Check that we accept lots of digits | |
| 40 assertEquals(Date.parse("2010-11-25T22:02:30.999Z"), Date.parse("2010-11-25T22:0 2:30.999999999999999999999999999999999999999999999999999999999999999999999999999 99999999999Z")); | |
| 41 // Fail if string has decimal point but zero digits for milliseconds | |
| 42 assertTrue(isNaN(Date.parse("2010-11-25T22:02:30.Z"))); | |
| OLD | NEW |