Re: ANNOUNCE: glibmm 2.33.12
- From: Kjell Ahlstedt <kjell ahlstedt bredband net>
- To: a gander <agander gmail com>
- Cc: gtkmm-list gnome org
- Subject: Re: ANNOUNCE: glibmm 2.33.12
- Date: Fri, 14 Sep 2012 16:43:08 +0200
2012-09-13 23:58, a gander skrev:
Just to check that I'm on the right track...
From the build messages I got:
gmmproc: Unwrapped functions:
gmmproc: g_bytes_unref_to_data
gmmproc: g_bytes_new_from_bytes
gmmproc: g_bytes_unref_to_array
gmmproc: Unwrapped functions:
gmmproc: g_iconv_close
gmmproc: Unwrapped functions:
gmmproc: g_iconv_close
gmmproc: Unwrapped functions:
gmmproc: g_iconv_close
And after checking for g_iconv_close, for instance, which has 11
mentions, I discover that it is called in ~IConv.
Is that what you would expect?
i.e. that that is the only place you would expect to see it?
Yes, this is as it should be. Don't bother with g_iconv_close().
10 .hg files contain the comment
// For some reason gmmproc thinks that g_iconv should be wrapped here.
_IGNORE(g_iconv)
Obviously gmmproc misunderstands some info somewhere, and thinks
g_iconv_close() also ought to be wrapped in a lot of places. I'll see if
I can understand why gmmproc behaves as it does, and if it can be easily
corrected.
Kjell
I'm still green here obviously and basically grepping for the function
in the build tree (*.{c,h,ccg,hg}) and cross-referencing in the Glib
devhelp docs.
Giles
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]