The library now requires GNU make, C90, and POSIX.1 compliance

Dec 22, 2013 21:15 GMT  ·  By

The second development release towards GLib 2.40 stable library, used in the GNOME desktop environment, has been released a few days ago, bringing lots of fixes and improvements.

First of all, we need to mention that GLib 2.39.2 removes alleged support for the OS/2, BeOS and last-millennium UNIXes, and it now requires C90 compliance, the GNU make compiler, as well as the POSIX.1 (1990) compliance on UNIX systems.

Second of all, GLib 2.39.2 now supports the "nonnull" attribute, adds the g_ptr_array_remove_range () function, no longer uses g_critical for a runtime error, supports compilation with Clang 3.2, fixes some crashes at startup, removes the g_trap_object_ref function, and allows for a clean and simple use of the g_test_trap_subprocess() function.

Moreover, the check for growing stack pointer in configure will no longer fail, the documentation now mentions property notification order, fixes copy issues with the g_file_replace_contents_async function, fixes leak with g_variant_builder_add's doc example, g_hash_table_add() now returns a boolean, gdbus-codegen now looks for dependencies in the default install path, and a reference leak in GvariantBuilder documentation has been fixed.

Also, the g_get_current_dir() function now checks PWD env var and returns it if it's correct, the GObject Introspection annotations have been added to genums.c, some mainloop instrumentation has been fixed, test failures on the PowerPC architecture have been fixed, various test programs can now be built on Windows/MSVC, and a basic test for the GNotification GTK backend has been added.

Last but not least, the Italian, Lithuanian, Simplified Chinese, and Spanish translations have been updated in GLib 2.39.2. Feel free to take a look at the official raw changelog if you want to know more about this development release of the powerful GLib library.

Download GLib 2.39.2 right now from Softpedia. Remember that this is a development version and it should NOT be installed on production machines. It is intended for testing purposes only.