This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | belopolsky |
|---|---|
| Recipients | belopolsky, christian.heimes, rolland |
| Date | 2008年03月25日.14:30:58 |
| SpamBayes Score | 0.04939681 |
| Marked as misclassified | No |
| Message-id | <1206455460.09.0.852988764434.issue2443@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
This is not a bug. All the reported functions expect va_list argument
to be initialized before being called. AFAICT, they are consistently
used in this way. For example,
PyObject *
PyObject_CallFunctionObjArgs(PyObject *callable, ...)
{
PyObject *args, *tmp;
va_list vargs;
if (callable == NULL)
return null_error();
/* count the args */
va_start(vargs, callable);
args = objargs_mktuple(vargs);
va_end(vargs);
if (args == NULL)
return NULL;
tmp = PyObject_Call(callable, args, NULL);
Py_DECREF(args);
return tmp;
}
This may need to be clarified in the docs. For example, PyString_FromFormatV does not mention that vargs needs to be
initialized: <http://docs.python.org/dev/c-
api/string.html#PyString_FromFormatV>. On the other hand, this may be
obvious to most C programmers.
I suggest to close this issue as invalid. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年03月25日 14:31:00 | belopolsky | set | spambayes_score: 0.0493968 -> 0.04939681 recipients: + belopolsky, christian.heimes, rolland |
| 2008年03月25日 14:31:00 | belopolsky | set | spambayes_score: 0.0493968 -> 0.0493968 messageid: <1206455460.09.0.852988764434.issue2443@psf.upfronthosting.co.za> |
| 2008年03月25日 14:30:58 | belopolsky | link | issue2443 messages |
| 2008年03月25日 14:30:58 | belopolsky | create | |