chl
99d8fc975e
Tightening the number parsing algorithm
...
Some badly formated "numbers" could get partly parsed,
resulting in truncated results instead of raising an
error.
Examples :
'1.2.3' -> (double)1.2
'2015-01-15' -> (int)2015
This patch is not perfect (ex: input can still end with a 'E', which
is forbidden by json.org doc) but should avoid non-sensically
formated input.
Tests added.
2015-02-05 01:50:37 +01:00
..
2014-03-22 21:40:37 -04:00
2013-02-09 16:35:24 -06:00
2012-04-28 14:14:26 -05:00
2012-11-29 15:06:17 -05:00
2012-09-16 20:49:22 -05:00
2012-04-28 14:14:26 -05:00
2012-09-16 20:49:22 -05:00
2012-09-16 20:49:22 -05:00
2012-09-16 20:49:22 -05:00
2012-09-16 20:43:29 -05:00
2012-04-22 10:33:41 -05:00
2012-04-28 14:14:26 -05:00
2012-04-28 14:14:26 -05:00
2012-04-28 14:14:26 -05:00
2012-04-28 14:14:26 -05:00
2012-09-16 20:43:29 -05:00
2012-04-22 10:33:41 -05:00
2012-04-22 10:33:41 -05:00
2012-09-16 20:43:29 -05:00
2012-04-22 10:33:41 -05:00
2012-04-22 10:33:41 -05:00
2014-03-22 21:15:41 -04:00
2014-03-22 21:15:41 -04:00
2014-03-22 21:15:41 -04:00
2012-12-13 11:46:04 +01:00
2013-09-11 20:27:39 -05:00
2013-02-26 21:14:07 -06:00
2012-12-23 10:25:03 -06:00
2012-12-23 10:25:03 -06:00
2012-04-22 10:33:41 -05:00
2012-07-29 12:13:54 -05:00
2012-07-29 12:13:54 -05:00
2014-03-22 21:40:37 -04:00
2015-02-05 01:50:37 +01:00
2015-02-05 01:50:37 +01:00
2012-04-22 10:33:41 -05:00
2013-02-09 16:35:24 -06:00
2012-04-22 14:25:08 -05:00
2012-04-22 14:13:01 -05:00
2012-09-16 20:43:29 -05:00
2012-09-09 13:53:12 -05:00
2012-09-02 15:21:56 -05:00
2012-04-28 14:14:26 -05:00
2013-02-21 12:32:29 -06:00
2012-10-20 20:26:37 -05:00
2012-07-24 23:27:41 -05:00