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 682969 - girparser: Track methods/constructors by symbol
girparser: Track methods/constructors by symbol
Status: RESOLVED FIXED
Product: gobject-introspection
Classification: Platform
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: gobject-introspection Maintainer(s)
gobject-introspection Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2012-08-29 18:00 UTC by Jasper St. Pierre (not reading bugmail)
Modified: 2015-02-07 17:02 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
ast: Remove what looks to be a copy/paste error (958 bytes, patch)
2012-08-29 18:00 UTC, Jasper St. Pierre (not reading bugmail)
committed Details | Review
girparser: Track methods/constructors by symbol (3.18 KB, patch)
2012-08-29 18:00 UTC, Jasper St. Pierre (not reading bugmail)
committed Details | Review

Description Jasper St. Pierre (not reading bugmail) 2012-08-29 18:00:31 UTC
We need to this so that we can calculate links by symbol, e.g.
doc_examples_obj_new() in doc comments. It's a set of potentially
dangerous changes. All tests pass, but I'm not quite sure of the
history here. I couldn't spot any differences in GLib/Gio/GObject,
either.
Comment 1 Jasper St. Pierre (not reading bugmail) 2012-08-29 18:00:33 UTC
Created attachment 222815 [details] [review]
ast: Remove what looks to be a copy/paste error

A symbol isn't a ctype. None of the tests failed when I removed
this, git blame wasn't very enlightening, and we don't remove this
in the remove method, so I'm thinking it's an error.
Comment 2 Jasper St. Pierre (not reading bugmail) 2012-08-29 18:00:36 UTC
Created attachment 222816 [details] [review]
girparser: Track methods/constructors by symbol

In order to be able to linkify a constructor/method, we need
to first track it by symbol.
Comment 3 Colin Walters 2012-08-30 01:56:26 UTC
Review of attachment 222815 [details] [review]:

Hmmmm.  Were you just reading the code and thought this was odd?

This is tingling a vague memory for me.  Something like structs having a "symbol" attribute and wanting to look them up by ctype too?  

Certainly commit 36aa515f isn't going to be helpful here =(  But trust me, the code was a lot worse before that...

Well, let's just kill it and see what happens I guess.  That's about the level of technology we have.
Comment 4 Colin Walters 2012-08-30 02:04:30 UTC
Review of attachment 222816 [details] [review]:

No, unless I'm totally misunderstanding, the documentation tool should just use Transformer.split_csymbol().  Adding included symbols to the current namespace is wrong.
Comment 6 Jasper St. Pierre (not reading bugmail) 2012-08-30 02:05:51 UTC
(In reply to comment #4)
> Review of attachment 222816 [details] [review]:
> 
> No, unless I'm totally misunderstanding, the documentation tool should just use
> Transformer.split_csymbol().  Adding included symbols to the current namespace
> is wrong.

Why is that? When we parse with the transformer, we float methods and constructors, which explicitly leaves it in self._symbols. Do you want me to just have a method that adds it to the symbols without the other things?
Comment 7 Colin Walters 2012-08-30 02:23:23 UTC
Review of attachment 222816 [details] [review]:

Reading this again, I see what you meant.  It makes sense.
Comment 8 Jasper St. Pierre (not reading bugmail) 2012-08-30 02:26:52 UTC
Attachment 222815 [details] pushed as 2081ad2 - ast: Remove what looks to be a copy/paste error
Attachment 222816 [details] pushed as 4f6f32d - girparser: Track methods/constructors by symbol


Pushed, along with a bunch of other doctool changes. Thanks!

I'm hoping that the new doc tool will be ready to replace gtk-doc for 3.8/3.10.
Comment 9 André Klapper 2015-02-07 17:02:34 UTC
[Mass-moving gobject-introspection tickets to its own Bugzilla product - see bug 708029. Mass-filter your bugmail for this message: introspection20150207 ]