On 5/14/08, Kirill Smelkov <[EMAIL PROTECTED]> wrote: > You know, when developing code, it is very tedious to look for meaningful > errors and warnings in presence of tons of noise like > warning: deprecated conversion from string constant to ‘char*’
Indeed! > And you know what? It seems in the next version of gcc, this deprecation > warnings will be turned into errors. > Python sources already use 'const' keyword freely, so I think it's time to > add > constify bits all over the place. Still Python sources does not use const at all the places they should. If that's the future of GCC, then Python 2.X series is going to need special compiler flags to disable this error. And I did not reviewed the status of Python 3 If you feel confident and have the time, try to build python 3 from sources using the -Wwrite-strings option for GCC. And if you are completelly sure that this will be and error in future GCC's, I believe you should warn about this in Python-Dev list... Some time agoo I tried to patch python2.6 so fix the 'const' issue. But it turned that this were going to introduce heavy source code compatibility problems in extension modules written for the 2.X series, so I give up. -- Lisandro Dalcín --------------- Centro Internacional de Métodos Computacionales en Ingeniería (CIMEC) Instituto de Desarrollo Tecnológico para la Industria Química (INTEC) Consejo Nacional de Investigaciones Científicas y Técnicas (CONICET) PTLC - Güemes 3450, (3000) Santa Fe, Argentina Tel/Fax: +54-(0)342-451.1594 _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
