Low-level core library that forms the basis for projects such as GTK+ and GNOME.
Go to file
Thomas Haller 4a709d0b46 ghash: comment g_hash_table_steal_extended() about not destroying key/value
The previous text was technically correct, but not very clear what
happens with the ownership of the key/value if it was not returned.
Elaborate on the fact, that the key/value is never destroyed, even if
not requested by the user.

I intuitively expected the function to behave differently, that is, to
destroy the key/value if (and only if) it was not returned. That is,
when the function does not return a pointer, then it would destroy it.
That would seem more consistent to me, where ownership is either
transferred to the caller, or the resource destroyed during the steal.

On the other hand, the existing behaviors is:

- is consistent with g_hash_table_steal() and never destroys key/value.
- behaves the same, regardless whether the key/value was returned.

So the existing behavior may be better.

Just elaborate on that detail in the doc.
2022-10-18 13:57:43 +01:00
.gitlab-ci ci: Conform to Python's coding style 2022-09-25 18:51:22 +01:00
.reuse docs: Mark .wrap files as uncopyrightable 2022-07-05 12:15:15 +01:00
docs Merge branch 'wip/chergert/g_set_str' into 'main' 2022-10-15 22:30:18 +00:00
fuzzing meson: fix build without cpp toolchain 2022-07-15 12:58:41 -06:00
gio Merge branch 'wip/pwithnall/2781-desktop-app-info-proc-bsd' into 'main' 2022-10-18 12:33:20 +00:00
glib ghash: comment g_hash_table_steal_extended() about not destroying key/value 2022-10-18 13:57:43 +01:00
gmodule Merge branch 'wip/smcv/deprecated-prop-followup' into 'main' 2022-10-15 21:31:29 +00:00
gobject Merge branch 'w32-tests' into 'main' 2022-10-17 09:53:44 +00:00
gthread Fix symbol visibility macros on Windows 2022-10-13 20:53:56 -04:00
LICENSES docs: Add all used licenses in a REUSE-compatible directory 2022-05-17 17:23:34 +01:00
m4macros m4macros: Increment serial number of glib-2.0.m4 2021-01-27 11:55:37 +00:00
po Update Hebrew translation 2022-10-06 13:23:20 +00:00
subprojects replace pcre1 with pcre2 2022-07-12 11:46:34 +00:00
tests Convert tests/assert-msg-test* to glib/tests/assert-msg-test* 2022-06-28 11:19:21 +01:00
tools tools: Reformat gen-visibility-macros.py with black 2022-10-14 18:15:25 +01:00
.clang-format CI: Code check formating in CI 2019-11-21 14:03:01 -06:00
.dir-locals.el Add .dir-locals.el to tell Emacs users not to use tabs for C 2012-07-30 04:09:08 -04:00
.editorconfig docs: Add .editorconfig file 2021-10-28 14:47:53 +01:00
.gitignore docs: Move INSTALL.in to INSTALL.md 2022-05-11 13:02:49 +01:00
.gitlab-ci.yml Merge branch 'ignore-dirs-leaks+valgrind-ci' into 'main' 2022-10-10 12:01:49 +00:00
.gitmodules build: Move gvdb to a subproject 2022-06-16 10:12:07 +01:00
.lcovrc build: Move lcovrc file to root so it’s picked up by Meson 2022-04-28 11:57:45 +01:00
CODE_OF_CONDUCT.md docs: Add a code of conduct document 2022-05-11 12:30:58 +01:00
CONTRIBUTING.md docs: Add a testing policy 2022-06-14 15:19:32 +01:00
COPYING docs: Add all used licenses in a REUSE-compatible directory 2022-05-17 17:23:34 +01:00
glib.doap docs: Sync glib.doap to set of users listed in CODEOWNERS 2022-06-22 15:54:49 +01:00
HACKING docs: Move README.rationale to docs subdirectory 2022-05-11 13:02:49 +01:00
INSTALL.md docs: Reformat INSTALL.md as Markdown 2022-05-11 13:02:55 +01:00
meson_options.txt gio: Optionally install trigger executables to architecture-specific paths 2022-07-24 11:19:37 +01:00
meson.build Merge branch 'wip/smcv/deprecated-prop-followup' into 'main' 2022-10-15 21:31:29 +00:00
msvc_recommended_pragmas.h msvc_recommended_pragmas.h: Refine for clang-cl 2021-03-30 16:45:07 +08:00
NEWS 2.74.0 2022-09-17 20:38:17 +02:00
README.md docs: Move INSTALL.in to INSTALL.md 2022-05-11 13:02:49 +01:00
README.win32.md README.win32.md: Mention about Window 8+ SDK requirement 2021-02-28 11:04:29 +02:00
SECURITY.md docs: Add a note about git-evtag to SECURITY.md 2021-09-07 11:21:12 +00:00

GLib

GLib is the low-level core library that forms the basis for projects such as GTK and GNOME. It provides data structure handling for C, portability wrappers, and interfaces for such runtime functionality as an event loop, threads, dynamic loading, and an object system.

The official download locations are: https://download.gnome.org/sources/glib

The official web site is: https://www.gtk.org/

Installation

See the file 'INSTALL.md'

Supported versions

Only the most recent unstable and stable release series are supported. All older versions are not supported upstream and may contain bugs, some of which may be exploitable security vulnerabilities.

See SECURITY.md for more details.

Documentation

API documentation is available online for GLib for the:

Discussion

If you have a question about how to use GLib, seek help on GNOMEs Discourse instance. Alternatively, ask a question on StackOverflow and tag it glib.

Reporting bugs

Bugs should be reported to the GNOME issue tracking system. You will need to create an account for yourself. You may also submit bugs by e-mail (without an account) by e-mailing incoming+gnome-glib-658-issue-@gitlab.gnome.org, but this will give you a degraded experience.

Bugs are for reporting problems in GLib itself, not for asking questions about how to use it. To ask questions, use one of our discussion forums.

In bug reports please include:

  • Information about your system. For instance:
    • What operating system and version
    • For Linux, what version of the C library
    • And anything else you think is relevant.
  • How to reproduce the bug.
    • If you can reproduce it with one of the test programs that are built in the tests/ subdirectory, that will be most convenient. Otherwise, please include a short test program that exhibits the behavior. As a last resort, you can also provide a pointer to a larger piece of software that can be downloaded.
  • If the bug was a crash, the exact text that was printed out when the crash occurred.
  • Further information such as stack traces may be useful, but is not necessary.

Contributing to GLib

Please follow the contribution guide to know how to start contributing to GLib.

Patches should be submitted as merge requests to gitlab.gnome.org. If the patch fixes an existing issue, please refer to the issue in your commit message with the following notation (for issue 123):

Closes: #123

Otherwise, create a new merge request that introduces the change. Filing a separate issue is not required.

Default branch renamed to main

The default development branch of GLib has been renamed to main. To update your local checkout, use:

git checkout master
git branch -m master main
git fetch
git branch --unset-upstream
git branch -u origin/main
git symbolic-ref refs/remotes/origin/HEAD refs/remotes/origin/main