Martin v. L=F6wis wrote: > "M.-A. Lemburg" <mal@lemburg.com> writes: >=20 >=20 >>I would accept that point if you could demonstrate a single >>case where the const nature of the filename actually does any >>good for the *user*. >=20 > See the original bug report. It avoids having to write const_casts. Great and now those who want to avoid warnings have to patch their old code :-( >>BTW, how can I silence warnings when writing C code that's >>supposed to compiler with Python 2.1 and 2.3 ? (passing const char * >>to a char * API doesn't work for obvious reasons) >=20 > Can you explain where such silencing would be necessary, for the > specific patch in question? It is not, because non of the variables > that got const now are ever passed to 2.1 API: they are all internal > to the core. They are ? The pythonrun.h changes were public in 2.1 as well and they include some of the more common APIs like the PyRun_*() APIs. --=20 Marc-Andre Lemburg CEO eGenix.com Software GmbH _______________________________________________________________________ eGenix.com -- Makers of the Python mx Extensions: mxDateTime,mxODBC,... Python Consulting: http://www.egenix.com/ Python Software: http://www.egenix.com/files/python/
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4