Re: Too many args to GTK2.TextBuffer "mark_set" signal

On Sat, Mar 15, 2014 at 11:17 PM, Chris Angelico <[email protected]> wrote:
> I've tracked down what's happening. In
> pgtk2_push_object_param(), there are a number of branches, most of
> which result in something being pushed; but one doesn't, and the
> TextIter hits that one. I've attached a simple patch that fixes the
> immediate issue by pushing the type name - so instead of getting a
> GTK2.TextIter object, you get the string "GtkTextIter". That fills in
> the spot on the stack, ensures that refcounts are correct, and so on,
> but it's not really ideal.

Anybody have opinions on the best solution to this? I think it's
fairly safe to say that the current Russian Roulette with refcounts is
less than ideal, and that passing the exact same number of arguments
to a Pike callback as would be expected based on the C docs is a
worthwhile goal, so the main question is what to push. The
aforementioned patch is fairly simple, and at least makes it clear
what's going on.

ChrisA