9 Commits

Author	SHA1	Message	Date
waldemar	5a99338f59	Fixed compiler warning	1998-06-11 20:27:22 +00:00
waldemar	d101f134c6	Fixed bugs 123565, 123874, 122877, 122882, 123560, and 77391, all having to do with various errors in reading integers and floating-point numbers and interpreting whitespace around them. Whitespace was being treated inconsistently in parseInt, parseFloat, and ToNumber; made all of these accept any Unicode whitespace in anticipation of the future ECMA v2.	1998-06-10 21:18:05 +00:00
mccabe	3bb24dc54d	Reinstated backed-out changes.	1998-06-03 06:08:21 +00:00
sar	0f5c5f61ce	backing out mccabes checkin	1998-06-03 02:30:46 +00:00
mccabe	bd33441b8b	Cleanup of parseInt checkin, including comment changes. The code is ... now a little more explit about when it expects js strings to be null-terminated.	1998-06-02 23:21:08 +00:00
fur	48ee6259d3	Merge several bug fixes from client 4.1 branch	1998-06-01 00:31:59 +00:00
waldemar	37b1e0ef09	Fixed syntax errors	1998-05-26 21:25:41 +00:00
mccabe	3f3c44a66d	Fix to (83996), global parseInt function fails for numbers > 2^31. ... It now passes all of the tests in 15.1.2.2-1 (except that parseInt still has the .length property, which is a different bug) - so I'll close the bug. Still possibly at issue is whether we conform to ECMA language about decimal numbers that are too large to fit in a double. I treat decimal digits after the 20th as zero, but there could be some floating-point rounding wackiness going on. In particular - are we doing the right thing for numbers that are powers of 2, but larger than 2^54, that are representable in a double?	1998-05-21 23:15:24 +00:00
fur	6b433caaaa	(This code is not built by any flavor of Navigator) ... Initial check-in to mozilla tree: JSRef development is migrating from JSFUN13_BRANCH of /m/src repository to /m/pub	1998-04-24 01:35:13 +00:00