[issue1772673] Replacing char* with const char*

[Eli Bendersky]

Eli Bendersky added the comment:

For external APIs visible to user code, this can cause some compatibility problems and users may need to at the very least re-compile this code. So -1 here.

For new external APIs, having const wherever appropriate should be considered on a case by case basis.

For internal code this is a good idea, but I wouldn't go mass-slashing all the code base now replacing char* by const char*. Presenting some examples where this makes sense in particular would be interesting though. +0

----------
nosy: +eli.bendersky

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue1772673>
_______________________________________