minor omission that effectively disabled my_strtod fixed :)

Author: serg@serg.mylan

mysql-test/r/bigint.result

@@ -84,3 +84,6 @@ quantity
 10000000000000000000
 10000000000000000000
 drop table t1;
+SELECT '0x8000000000000001'+0;
+'0x8000000000000001'+0
+0

mysql-test/r/func_misc.result

@@ -1,6 +1,6 @@
 select format(1.5555,0),format(123.5555,1),format(1234.5555,2),format(12345.5555,3),format(123456.5555,4),format(1234567.5555,5),format("12345.2399",2);
 format(1.5555,0)	format(123.5555,1)	format(1234.5555,2)	format(12345.5555,3)	format(123456.5555,4)	format(1234567.5555,5)	format("12345.2399",2)
-2	123.6	1,234.56	12,345.556	123,456.5555	1,234,567.55550	12,345.24
+2	123.6	1,234.56	12,345.555	123,456.5555	1,234,567.55550	12,345.24
 select inet_ntoa(inet_aton("255.255.255.255.255.255.255.255"));
 inet_ntoa(inet_aton("255.255.255.255.255.255.255.255"))
 NULL

mysql-test/t/bigint.test

@@ -69,5 +69,5 @@ select * from t1;
 drop table t1;
 
 # atof() behaviour is different of different systems. to be fixed in 4.1
-#SELECT '0x8000000000000001'+0;
+SELECT '0x8000000000000001'+0;
 

strings/strtod.c

@@ -135,6 +135,6 @@ double my_strtod(const char *str, char **end)
 
 double my_atof(const char *nptr)
 {
-  return (strtod(nptr, 0));
+  return (my_strtod(nptr, 0));
 }