[Github-comments] [geany/geany] Gi signals (#1038)

Matthew Brush notifications at xxxxx
Tue May 17 00:40:24 UTC 2016


IMO, we shouldn't abuse GBoxed like that. Would be better to fix upstream to work properly than spread bug-generating hacks all over. Isn't there also some kind of annotation comment that can be used to hint gir-scanner that the parameter is just a raw pointer with a `G_TYPE_POINTER`?

I'm not super fond of exposing the GeanyObject either. IMO, if it _must_ be exported to make this work, we shouldn't add Doxygen comments so it remains "private" and we can drop at will whenever we get around to moving those signals to the correct objects.

I think this PR also depends on changes that are being worked on upstream, so the Travis builds fail.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/1038#issuecomment-219589344
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.geany.org/pipermail/github-comments/attachments/20160516/1b0b5315/attachment.html>


More information about the Github-comments mailing list