[Python-Dev] Baffled by PyArg_ParseTupleAndKeywords modification
Jeremy Hylton
jeremy at alum.mit.edu
Fri Feb 10 19:05:41 CET 2006
On 2/10/06, Tim Peters <tim.peters at gmail.com> wrote:
> [Jeremy]
> I added some const to several API functions that take char* but
> typically called by passing string literals.
>
> If he had _stuck_ to that, we wouldn't be having this discussion :-)
> (that is, nobody passes string literals to
> PyArg_ParseTupleAndKeywords's kws argument).
They are passing arrays of string literals. In my mind, that was a
nearly equivalent use case. I believe the C++ compiler complains
about passing an array of string literals to char**.
Jeremy
More information about the Python-Dev
mailing list