Re: [Evolution-hackers] detecting new ical memory tracking

[Matthew Barnes <mbarnes redhat com>]

On Tue, 2008-04-08 at 21:42 +0200, Patrick Ohly wrote:
> Introducing the code rewrite suggested by Michael is impossible. Can I
> have the less intrusive patch included on trunk and the stable branch,
> please? Or is there some other version number which can be queried at
> runtime? I'd rather not parse /proc/self/maps to find out what the
> revision of libecal is... As discussed in #516408, checking the version
> number would be sub-optimal.

More broadly, we should add some versioning macros and symbols to
libedataserver similar to [1], so Patrick could do something like:

#if EDS_CHECK_VERSION(2,22,0)
    ... free libical strings ...
#endif

Would that address your needs, Patrick?

Matthew Barnes


[1]
http://library.gnome.org/devel/glib/unstable/glib-Version-Information.html