cast_object_to bug / PerlQt cvs compilation (Was Re: [Kde-bindings] [Bug 71316] QtRuby : Segmentation fault when loading Qt)
lypanov at kde.org
Tue Jan 13 10:23:01 UTC 2004
On Tue, Jan 13, 2004 at 09:56:54AM +0000, Richard Dale wrote:
> On Tuesday 13 January 2004 09:43, Alexander Kellett wrote:
> > oh, aaah. so thats why the constant wasn't working,
> > i was still trying to debug this last night but got
> > no further. i'm making these sorts of errors really
> > frequently so i'm gonna stick something in there
> > to print a list of matched classes on such failures
> Good idea, but only do that if a suitable debug flag is set, so the user has
> some control.
> 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" :)
> 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...
the branch name is : more_examples_branch
When women love us, they forgive us everything, even our crimes; when they do
not love us, they give us credit for nothing, not even our virtues.
-- Honor'e de Balzac
More information about the Kde-bindings