On Fri, Jan 2, 2009 at 12:58 AM, Adam Olsen <rha...@gmail.com> wrote: .. > > As C++ has more specific ways of allocating memory, they impose this > restriction to annoy you into using them.
And so does Python API: see PyMem_NEW and PyMem_RESIZE macros. > We won't be using them, and the extra casts and nothing but noise. A quick grep through the sources shows that these casts are not just nose: Objects/stringobject.c: op = (PyStringObject *)PyObject_MALLOC(.. Objects/typeobject.c: remain = (int *)PyMem_MALLOC(.. Objects/unicodeobject.c: unicode->str = (Py_UNICODE*) PyObject_MALLOC(.. in many cases the type of object being allocated is not obvious from the l.h.s. name. Redundant cast improves readability in these cases. > Figure out a way to turn off the warnings instead. > These are not warnings: these are compile errors in C++. A compiler which allows to suppress them would not be a standard compliant C++ compiler. _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
