RetroSearch Browse

Tue Feb 14 07:30:16 CET 2006 · https://mail.python.org/pipermail/python-dev/2006-February/060883.html

Jeremy Hylton wrote:
> The compiler in question is gcc and the warning can be turned off with
> -Wno-write-strings.  I think we'd be better off leaving that option
> on, though.  This warning will help me find places where I'm passing a
> string literal to a function that does not take a const char*.  That's
> valuable, not insensate.

Hmm. I'd say this depends on what your reaction to the warning is.
If you sprinkle const_casts in the code, nothing is gained.

Perhaps there is some value in finding functions which ought to expect
const char*. For that, occasional checks should be sufficient; I cannot
see a point in having code permanently pass with that option. In
particular not if you are interfacing with C libraries.

Regards,
Martin

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2006-February/060883.html below:

[Python-Dev] Baffled by PyArg_ParseTupleAndKeywords modification