[Gtk-sharp-list] Announcing Gtk# releases 2.5.5 and 1.9.5

Ben Maurer bmaurer at ximian.com
Fri May 20 00:13:26 EDT 2005

On Thu, 2005-05-19 at 20:54 -0700, Todd Berman wrote:
> On Thu, 2005-05-19 at 23:03 -0400, Miguel de Icaza wrote:
> > Hello,
> > 
> > > This is a helpful reference to know what apis are new in GTK 2.6 (and
> > > thus would *not* be available on gtk# 1.9.x):
> > > 
> > > http://developer.gnome.org/doc/API/2.0/gtk/ix05.html
> > 
> > I wonder if we should have a tag for differences in the APIs between
> > 1.9.x and 2.5.x and have mcs emit a warning if the 2.5.x stuff is used.
> > 
> Please no. Some of us actually use 2.5.x for reasons that make sense for
> them.
> That would make it very difficult to work for me.
> Can we add error codes though (that would work with the nowarn stuff w/
> csc)? We build both with csc and mcs, and if you could tell it to ignore
> those new warning codes, I guess it would be fine, although I am not
> sure that it would be good. It is one thing to say "we don't recommend
> using it" and it is another to start causing tons of debug spew to say
> that over and over again :)

The only way it would ever work with csc is to (ab)use Obsolete:

[Obsolete ("This api is too new!")]

The cost of that would be:
      * You either turn off the obsolete warnings altogether and don't
        get the ones that are useful to you, or you get a spew of
      * The error message is somewhat amusing

The other option would be:

[__GtkApiVersion ("2.4")] and you pass mcs a -req-gtk 2.2 and it warns
if you use any new functionality. However, that clearly won't work on

We gain a bit of control here, at the cost of the thing working with

-- Ben

More information about the Gtk-sharp-list mailing list