cast_object_to bug / PerlQt cvs compilation (Was Re: [Kde-bindings] [Bug 71316] QtRuby : Segmentation fault when loading Qt)
Richard_Dale at tipitina.demon.co.uk
Tue Jan 13 10:55:20 UTC 2004
On Tuesday 13 January 2004 10:23, Alexander Kellett wrote:
> > I removed it because I thought it improved the error messages. What is
> > the difference between qtruby indicating a method is missing, and the
> > normal ruby Object error - what do you mean by 'real error'? That should
> > only be for subclasses of Qt:: which don't have non-Qt behaviour to
> > preserve, not all ruby classes.
> qtruby catches all missing variables in subclasses, therefore the
> user sees "couldn't resolve method" instead of "you mistyped blah" :)
So it sounds as though the problem is just for const_missing() originated
calls? Although both missing methods and missing constants end up calling the
same qtruby missing_method handler. Maybe only call super is the missing item
starts with an uppercase letter, or give a different error message than for
things which look like methods.
> > I've no idea why we have to put examples in a branch, rather than
> > straight in HEAD, when the project isn't built be default. What's the
> > branch called it - I'll have a look?
> i'd prefer to keep my commits out of the main version to keep
> coolo's work down - i guess he is tracking all changes and
> tagging important ones...
Good point, I didn't know that was involved.
> the branch name is : more_examples_branch
ok, I'll have a look.
More information about the Kde-bindings