[Python-Dev] Compiler warnings (original) (raw)
Robert Kim Wireless Internet Advisor evdo.hsdpa at gmail.com
Wed Feb 1 03:42:27 CET 2006
- Previous message: [Python-Dev] Compiler warnings
- Next message: [Python-Dev] Compiler warnings
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
u guys are way over my head :) bob
-- Robert Kim 2611s Highway 101 suite 102 San diego CA 92007 206 984 0880
http://evdo-coverage.com/cellular-repeater.html
On 1/31/06, Guido van Rossum <guido at python.org> wrote:
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
ewithout going through > > x = PyLongAsScaledDouble(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/)
Python-Dev mailing list Python-Dev at python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/evdo.hsdpa%40gmail.com
-- Robert Q Kim, Wireless Internet Advisor http://evdo-coverage.com/cellular-repeater.html http://hsdpa-coverage.com
2611 S. Pacific Coast Highway 101 Suite 102 Cardiff by the Sea, CA 92007 206 984 0880
- Previous message: [Python-Dev] Compiler warnings
- Next message: [Python-Dev] Compiler warnings
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]