DBUS introspection (Was: DCOP interface in kicker broke compatibility?)

Havoc Pennington hp at redhat.com
Wed Feb 2 12:41:40 PST 2005

On Wed, 2005-02-02 at 19:46 +0000, Mike Hearn wrote:
> On Wed, 02 Feb 2005 10:12:33 +0100, Waldo Bastian wrote:
> >> What would be nice would be if there was a flag for the method that would
> >> prevent it from showing up in the list of DCOP methods, but still be
> >> possible to call.  Or at least some way of marking parts of the DCOP API as
> >> deprecated...though I suppose it's a bit late for such.
> > 
> > Something to keep in mind for the DBUS introspection format.
> Why is that better than just marking it as deprecated in the
> documentation? They can't be removed until you next do a breaking release,
> and hiding them from the list of methods introspection shows would be a
> breaking change too. So I guess it'd be purely an advisory flag, but if
> you're going to do that why not put all the docs in the introspection data?

You could maybe do things like have a "warn if I use deprecated" mode in
the bindings, maybe. Some languages have a built-in feature for that
even I think. Not sure.


More information about the dbus mailing list