I see...
Here's a patch against what appears in the git tree, in case any
maintainer wants to apply it:
diff --git a/gio/src/memoryinputstream.hg b/gio/src/memoryinputstream.hg
index 2ad92bb..eb365ad 100644
--- a/gio/src/memoryinputstream.hg
+++ b/gio/src/memoryinputstream.hg
@@ -58,6 +58,8 @@ public:
*
* @param data Input data.
* @param len Length of the data, may be -1 if data is a
null-terminated string.
+ *
+ * @deprecated Use version with destroy notification
*/
void add_data(const void* data, gssize len);
@@ -68,7 +70,6 @@ public:
* @param destroy A function to be called to free the data when it is no
* longer needed
*
- * @deprecated Use version with destroy notification
*/
void add_data(const void* data, gssize len, GDestroyNotify destroy);
};
On 21 February 2010 22:34, Bill O'Connor <[email protected]> wrote:
>
> Michael <[email protected]> writes:
>
> > Hello. Consider those page:
> > http://library.gnome.org/devel/glibmm/stable/deprecated.html#_deprecate
> > d000002
> > http://library.gnome.org/devel/glibmm/stable/classGio_1_1MemoryInputStr
> > eam.html#aa26832ff7a8bce5cc15518d5a2f0a14b They say that add_data is
> > deprecated and that the version with destroy notification should be
> > used, but I don't see any other version with destroy notification. May
> > be I don't understand something... Could anyone clarify?
>
> Strange. It looks like the deprecation notice should have been attached
> to this member instead:
>
> void Gio::MemoryInputStream::add_data (
> const void * data,
> gssize len);
>
> So, it looks like you should use the member function that says it's
> deprecated. :)
>
> --
> In Solidarity,
> Billy O'Connor
_______________________________________________
gtkmm-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/gtkmm-list
