RetroSearch Browse

Fri Feb 10 19:05:41 CET 2006 · https://mail.python.org/pipermail/python-dev/2006-February/060704.html

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

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

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

[Python-Dev] Baffled by PyArg_ParseTupleAndKeywords modification