[Kde-bindings] Constructor error with QtRuby redux

[Richard Dale]

On Tuesday 06 December 2005 14:06, Caleb Tennis wrote:
> I just thought of one possibility here.  If for some reason the catch
> doesn't catch the throw, it will return a 'nil', and thus we'll get a
> 'nil' result, which obviously doesn't respond_to initialize.
>
> I guess worst case we'd just get an exception thrown, though, so it's
> probably not too bad.
If the first initialize() call returns Qnil, something has gone badly wrong 
and it should be a fatal error. But please add a test if you like.

-- Richard

> >> I can't see anything wrong with the test being removed - should we just
> >> do
> >> that? I've forgotten why I've included it in the first place, but it
> >> does
> >> seem redundant.
> >
> > Yeah, I can't see why it's necessary either.  Instances of Class seem to
> > have "initialize" defined, so I suppose an object will always respond_to
> > it.
> >
> > Caleb
> >
> > _______________________________________________
> > Kde-bindings mailing list
> > Kde-bindings at kde.org
> > https://mail.kde.org/mailman/listinfo/kde-bindings
>
> _______________________________________________
> Kde-bindings mailing list
> Kde-bindings at kde.org
> https://mail.kde.org/mailman/listinfo/kde-bindings