[Bug 22205] New: Allow not generating, or deprecating, _run_ methods

[bugzilla-daemon at freedesktop.org]

http://bugs.freedesktop.org/show_bug.cgi?id=22205

           Summary: Allow not generating, or deprecating, _run_ methods
           Product: Telepathy
           Version: unspecified
          Platform: Other
               URL: http://git.collabora.co.uk/?p=user/smcv/telepathy-glib-
                    smcv.git;a=shortlog;h=refs/heads/reentrant
        OS/Version: All
            Status: NEW
          Keywords: patch
          Severity: normal
          Priority: medium
         Component: telepathy-glib
        AssignedTo: telepathy-bugs at lists.freedesktop.org
        ReportedBy: simon.mcvittie at collabora.co.uk


11:52 < barisione> _run_ functions are evil

The reentrant methods in telepathy-glib client code turn out not to be such a
good idea.

Mission Control hasn't had them for a while, and has a slightly outdated fork
of glib-client-gen.py that supports a command-line option to not generate them
(and also a command-line option to generate blocking versions, but that's
WONTFIX from my point of view, and no longer used anyway).

If we add a similar command-line option to telepathy-glib's glib-client-gen.py,
we can replace MC's fork with the real one.

Also, in the long term (early in the 0.9 series?) we should deprecate _run_
altogether. I've added a command-line option to deprecate these methods, which
works per "class".

My plan is that when I add Client, ChannelDispatcher etc. bindings, they will
lack the _run_ methods altogether; existing classes will keep them, deprecate
them in 0.9.0, and delete them when we break ABI.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.