[Python-Dev] Baffled by PyArg_ParseTupleAndKeywords modification
Tim Peters
tim.peters at gmail.com
Fri Feb 10 18:27:35 CET 2006
More information about the Python-Dev mailing list
Fri Feb 10 18:27:35 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 ]
[Jeremy] >> It looks like a solution may be to define it as "const char * const *" >> rather than "const char **". I'll see if that works. [Jeremy] > No. It doesn't work. I'm not sure about this one either, but some > searching suggests that you can pass a char** to a function taking > const char* const* in C++ but not in C. Oops! I think that's right. > Sigh. I don't see any way to avoid a warning in Jack's case. Martin's turn ;-)
- 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 ]
More information about the Python-Dev mailing list