After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 573933 - Scanner should handle _full methods specially
Scanner should handle _full methods specially
Status: RESOLVED DUPLICATE of bug 556475
Product: gobject-introspection
Classification: Platform
Component: general
2.19.x
Other Linux
: Normal normal
: ---
Assigned To: gobject-introspection Maintainer(s)
gobject-introspection Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2009-03-03 15:59 UTC by Andreas Rottmann
Modified: 2015-02-07 16:55 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Andreas Rottmann 2009-03-03 15:59:07 UTC 
When a _full variant of a function is provided that only adds a destroy notification callback, I think the appropriate behavior of the scanner would be to:

- Discard the non-_full variant
- Remove the _full suffix from the exposed name
Comment 1 Johan (not receiving bugmail) Dahlin 2009-03-03 16:10:49 UTC 
I don't think the scanner should attempt to guess this behavior.

Instead we should add annotations which says that foo_full() should be exposed in the API as just foo().
Comment 2 Colin Walters 2009-03-03 16:52:11 UTC 
Yeah, this is the rename-to: bug, need to fix up that patch.

*** This bug has been marked as a duplicate of 556475 ***
Comment 3 André Klapper 2015-02-07 16:55:06 UTC 
[Mass-moving gobject-introspection tickets to its own Bugzilla product - see bug 708029. Mass-filter your bugmail for this message: introspection20150207 ]