Commit c4c1cbdf authored by Tim Peters's avatar Tim Peters

SF bug 119622: compile errors due to redundant atof decls. I don't understand

the bug report (for details, look at it), but agree there's no need for Python
to declare atof itself:  we #include stdlib.h, and ANSI C sez atof is declared
there already.
parent 48623af2
...@@ -767,7 +767,6 @@ com_addopname(struct compiling *c, int op, node *n) ...@@ -767,7 +767,6 @@ com_addopname(struct compiling *c, int op, node *n)
static PyObject * static PyObject *
parsenumber(struct compiling *co, char *s) parsenumber(struct compiling *co, char *s)
{ {
extern double atof(const char *);
char *end; char *end;
long x; long x;
double dx; double dx;
......
...@@ -403,7 +403,6 @@ r_object(RFILE *p) ...@@ -403,7 +403,6 @@ r_object(RFILE *p)
case TYPE_FLOAT: case TYPE_FLOAT:
{ {
extern double atof(const char *);
char buf[256]; char buf[256];
double dx; double dx;
n = r_byte(p); n = r_byte(p);
...@@ -422,7 +421,6 @@ r_object(RFILE *p) ...@@ -422,7 +421,6 @@ r_object(RFILE *p)
#ifndef WITHOUT_COMPLEX #ifndef WITHOUT_COMPLEX
case TYPE_COMPLEX: case TYPE_COMPLEX:
{ {
extern double atof(const char *);
char buf[256]; char buf[256];
Py_complex c; Py_complex c;
n = r_byte(p); n = r_byte(p);
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment