[Python-Dev] Baffled by PyArg_ParseTupleAndKeywords modification (original) (raw)
Jeremy Hylton jeremy at alum.mit.edu
Fri Feb 10 19:05:41 CET 2006
- Previous message: [Python-Dev] Baffled by PyArg_ParseTupleAndKeywords modification
- Next message: [Python-Dev] Baffled by PyArg_ParseTupleAndKeywords modification
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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 PyArgParseTupleAndKeywords'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
- Previous message: [Python-Dev] Baffled by PyArg_ParseTupleAndKeywords modification
- Next message: [Python-Dev] Baffled by PyArg_ParseTupleAndKeywords modification
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]