Re: segv on bad gobject get call

[muppet <scott asofyet org>]

On Dec 11, 2007, at 4:47 PM, Kevin Ryde wrote:

> "muppet" <scott asofyet org> writes:
> > gperl.h:249:#define SvGObject(sv)  (gperl_get_object_check (sv,  
> > G_TYPE_OBJECT))
> >
> > and, quite frankly, i don't know why it isn't.
>
> I couldn't tell if some uses were meant to have NULL getting through,
> say for those funcs where NULL is ok, and/or because a lot of funcs  
> will
> g_log or whatever for a NULL by themselves anyway.

That's why we have SvGObject_ornull().  I think this may be a long- 
overlooked bug.


--
zella (crying):  I want...
us:  What?
zella (still crying):  I want...  something!