[Github-comments] [geany/geany] Ctags sync, part 1 (#1160)

elextr notifications at xxxxx
Thu Aug 4 11:15:18 UTC 2016


@techee changing `g_` to plain POSIX has the following problems I'm aware of:

1. Changing anything that returns memory back to Geany from `g_*` to `malloc` means the frees inside Geany need to be changed from `g_free()` to` free()` since you can't mix them (according to the Glib [description section](https://developer.gnome.org/glib/stable/glib-Memory-Allocation.html))  It is going to be confusing if some memory in geany needs to be `g_free`d and some plain `free`d. And I hope none of that gets to the plugin API.

2. `g_strerror()` is different to POSIX in that its guaranteed UTF-8 whereas POSIX is locale dependent.  That means it needs conversion if its to be displayed in the UI.  OT not *all* `g_` string [changes](https://github.com/geany/geany/commit/084c23bbb163fd95d00e2032698ec3371d366693) were part of a global change :grin:

3. I believe `g_stat` etc work around much windows weirdness, which would have to be solved if the Glib version was not used.  (BTW why don't these get #605 type problems?)

"HTML parser? I'm too busy generating the [expletive deleted] stuff" which is why I don't have much Geany time lately.  Use the expat library.

IRO the new uctags parser: I understand it is intended to do local variables, but it didn't seem to provide them when I tried, and anyway what about scope for locals, and Geany does not understand scopes.  It would be a real mess if all locals were offered for completions all the time.



---
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/1160#issuecomment-237524652
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.geany.org/pipermail/github-comments/attachments/20160804/d9d50b8a/attachment.html>


More information about the Github-comments mailing list