Idiom for error checking within a C extension

[Jon Perez]

I want to retrieve a value from a tuple and convert it to a C
type. Is the following idiom okay?

if (!(
( tmp_pyobj=PyTup le_GetItem(tupl e,1) ) &&
( c_int=PyInt_AsL ong(tmp_pyobj) )
))
{
if (PyErr_Exceptio nMatches(PyExc_ TypeError))
PyErr_SetString (PyExc_TypeErro r,"tuple's 1st member was not an integer");
return NULL;
}
The PyErr_Exception Matches/PyErr_SetString combination in the if-block is
where I'm a bit unsure. I want to check if the tuple element is of the
correct type (a PyInt in this case) and if it isn't, I want to return my
own customized error message instead of the default TypeError message.
I'm kind of uncomfortable with the idea that I am checking for the kind
of exception raised and then afterwards calling a function which can
change it (even if I don't really end up doing that).

[David M. Cooke]

At some point, Jon Perez <jb********@yah oo.com> wrote:

I want to retrieve a value from a tuple and convert it to a C
type. Is the following idiom okay?

if (!(
( tmp_pyobj=PyTup le_GetItem(tupl e,1) ) &&
You've got 1 here, but mention the first member below (that's number 0).
( c_int=PyInt_AsL ong(tmp_pyobj) )
))
{
if (PyErr_Exceptio nMatches(PyExc_ TypeError))
PyErr_SetString (PyExc_TypeErro r,"tuple's 1st member was not an integer");
return NULL;
}
The PyErr_Exception Matches/PyErr_SetString combination in the if-block is
where I'm a bit unsure. I want to check if the tuple element is of the
correct type (a PyInt in this case) and if it isn't, I want to return my
own customized error message instead of the default TypeError message.
I'm kind of uncomfortable with the idea that I am checking for the kind
of exception raised and then afterwards calling a function which can
change it (even if I don't really end up doing that).

That's no different than the python code

try:
p = tple[0]
c = int(p)
except TypeError:
raise TypeError("tupl e's 1st member was not an integer")

You could use PyInt_Check(), and throw your own error, but if you want
to handle longs or things that can be coerced to ints, you end up
rewriting PyInt_AsLong().

--
|>|\/|<
/--------------------------------------------------------------------------\
|David M. Cooke
|cookedm(at)phy sics(dot)mcmast er(dot)ca