okay, i think i don't entirely understand when i should claim a reference using g_object_ref and when i shouldn't #GLib #GObject

question 1: should a function that returns a pointer to an object g_object_ref it for the caller's sake?

Important security update for GLib and D-Bus, thanks to @pwithnall

discourse.gnome.org/t/security…

If you are a downstream distributor of GLib, GTK, or GNOME-related projects, remember to follow the distributor tag on Discourse.

#glib #security

Security fixes for signal handling in GDBus in GLib

A series of related security fixes for how signal subscriptions are handled in GDBus have just landed in GLib.

^{GNOME Discourse}

Embloggeration happened: bassi.io/articles/2023/10/25/i…

In which I talk about the current plans for gobject-introspection and GLib.

If you work on language bindings, and/or packaging glib, you should reach out to the GLib maintainers.

#gnome #glib #gnome

Introspection’s edge

In which I go over the plans for gobject-introspection

^{halting problem}

Does anyone care deeply about macOS support for GLib? If so, you might want to get involved

gitlab.gnome.org/GNOME/glib/-/…

#GLib #macOS

ci: Disable the macOS CI (!3463) · Merge requests · GNOME / GLib · GitLab

It’s almost a complete waste of time at the moment. For several reasons, jobs flakily fail on it more often than they succeed. It’s wasting resources, slowing down...

^GitLab

If you’re using the GLib reference on docs.gtk.org and you’re missing the documentation for various C pre-processor macros, you can now find it here:

- docs.gtk.org/glib/macros.html
- docs.gtk.org/glib/conversion-m…
- docs.gtk.org/glib/auto-cleanup…

#gtk #glib #documentation