On Sat, 2005-12-17 at 05:21 -0600, Yevgen Muntyan wrote:
Tim Janik wrote:
On Fri, 16 Dec 2005, Murray Cumming wrote:
Thanks. But this is not completely clear to me yet.
Will applications built against gtk+ 2.6 work when gtk+ 2.10 is
installed, without rebuilding the applications?
Thanks. But this is not completely clear to me yet.
Will applications built against gtk+ 2.6 work when gtk+ 2.10 is
installed, without rebuilding the applications?
Murray Cumming
[EMAIL PROTECTED]
www.murrayc.com
www.openismus.com
___
gtk-devel-list
On Fri, 16 Dec 2005, Murray Cumming wrote:
Thanks. But this is not completely clear to me yet.
Will applications built against gtk+ 2.6 work when gtk+ 2.10 is
installed, without rebuilding the applications?
yes.
Murray Cumming
[EMAIL PROTECTED]
www.murrayc.com
www.openismus.com
---
Tim Janik wrote:
On Fri, 16 Dec 2005, Murray Cumming wrote:
Thanks. But this is not completely clear to me yet.
Will applications built against gtk+ 2.6 work when gtk+ 2.10 is
installed, without rebuilding the applications?
yes.
But old libgtkmm binary and applications that use it will
On Thu, 15 Dec 2005, Yevgen Muntyan wrote:
Tim Janik wrote:
ok so there is a reason. a desire (by multiple users and projects
actually) to implement that flag and a possibility (as was found out
in the original thread on this subject already).
Nobody so far said that objects with floating
Tim Janik wrote:
Nobody so far said that objects with floating reference in glib is
not needed.
But what about Murray idea, to create separate class; or, along same
lines,
that wouldn't change a thing. if you had a GFLoatableObject, you'd still
want to derive GtkObject from it, so you may
On Fri, 16 Dec 2005, Yevgen Muntyan wrote:
No, I do not think you are so bad that you write sucky floating reference
stuff in glib. Maybe this particular breakage is not that bad, and GObject
with floating reference is incredibly good for peace in the world.
once this thread has settled and
Tim Janik wrote:
in general, glib and gtk will remain source and binary backwards
compatible with
regards to the floating reference changes.
See below. And again, this thing with floating reference thing is a
precedent.
Broken twice (recent glib changes related to some crazy unicode stuff),
On Fri, 16 Dec 2005, Yevgen Muntyan wrote:
Tim Janik wrote:
It doesn't address issue of old code that uses GTK, that was written for old
GTK,
and/or was built with old GTK (like gtkmm, if I understand that issue
correctly).
it does, that is what this thread is about. the current code in
On Thu, 15 Dec 2005, Dave Benson wrote:
There is no problem in this combination. GTK+ 2.8 continues to use the
GtkObject floating flag,
and does not care about the GObject floating flag at all. We decided to
allow finalizing floating GObjects,
so there is no problem.
as long as no-one
On Thu, 15 Dec 2005, Dave Benson wrote:
On Fri, Dec 16, 2005 at 12:29:18AM +0100, Tim Janik wrote:
i think this is a good enough compromise. we'll allow potential breakage
if applications/libraries don't care to implement their dependencies
properly. i hope that is weak enough to not occour or
Tim Janik wrote:
ok so there is a reason. a desire (by multiple users and projects
actually) to implement that flag and a possibility (as was found out
in the original thread on this subject already).
Nobody so far said that objects with floating reference in glib is not
needed.
But what
12 matches
Mail list logo
