[Python-Dev] Compiler warnings
Guido van Rossum
guido at python.org
Wed Feb 1 02:59:54 CET 2006
More information about the Python-Dev mailing list
Wed Feb 1 02:59:54 CET 2006
- Previous message: [Python-Dev] Compiler warnings
- Next message: [Python-Dev] Compiler warnings
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 1/31/06, Tim Peters <tim.peters at gmail.com> wrote: > [Thomas Wouters] > > Objects/longobject.c:655: warning: 'e' may be used uninitialized in this function > > Well, that's pretty bizarre. There's _obviously_ no way to get to a > reference to `e` without going through > > x = _PyLong_AsScaledDouble(vv, &e); > > first. That isn't a useful warning. But how can the compiler know that it is an output-only argument? -- --Guido van Rossum (home page: http://www.python.org/~guido/)
- Previous message: [Python-Dev] Compiler warnings
- Next message: [Python-Dev] Compiler warnings
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list