[Github-comments] [geany] Gi sci methods (#935)

Colomban Wendling notifications at xxxxx
Sun Mar 6 21:19:22 UTC 2016


> I'd like to treat the .gir like a black box as far as possible because 
the format is not documented or stable, subject to change at any time. I 
don't consider the extra symbols to be that much of a problem to start 
processing the .gir.

I don't consider the format possible instability (which is rather theoretical as there are more than one tool that deal with it, so it's unlikely to change enough to break much things) not really a reason enough to drop in what I see as useless symbols.  And that we should maintain either manually or trusting a generation script that will parse C to generate actual code in the library.

And as a proof of concept, although it's indeed somewhat hacky, I successfully generated what looks like a proper GIR simply replacing a few symbols before and after: https://gist.github.com/b4n/75806eaaa87f3b0990a7
Sure it's not as neat as would be having everything recognized out of the box by g-ir-scanner, but it seems better to me than adding more complex stuff to sneak in extra symbols just to make it happy.

> Might be doable with the doxygen too.  The problem with a doxygen-based 
solution is that the doxygen output is generated after lingeany is 
built, basically too late to add symbols to it.

Fair point.

> If we can agree on shipping the symbols then I'd suggest to actually 
ship the .c file and deal with how to generate after the release (I'm 
not sure I'll manage to bring a doxygen-based solution in time).

POssibly, but I really would rather avoid that.

---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/935#issuecomment-192998243
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.geany.org/pipermail/github-comments/attachments/20160306/f3d6ea30/attachment.html>


More information about the Github-comments mailing list