From c309c65ecbaf6c92f4843a1a709f4414e32348b3 Mon Sep 17 00:00:00 2001 From: Owen Taylor Date: Tue, 16 Mar 2004 19:10:34 +0000 Subject: === Released 2.4.0 === Tue Mar 16 11:50:56 2004 Owen Taylor * === Released 2.4.0 === * configure.in: Version 2.4.0, interface age 0. * README.in: Updates * NEWS: Updates --- README.in | 35 +++++++++++++++++------------------ 1 file changed, 17 insertions(+), 18 deletions(-) (limited to 'README.in') diff --git a/README.in b/README.in index 56ab9aa7c..fae504f92 100644 --- a/README.in +++ b/README.in @@ -24,26 +24,25 @@ Installation See the file 'INSTALL' -Notes about GLib-2.2.0 +Notes about GLib-2.4.0 ====================== -* GLib changed the seeding algorithm for the pseudo-random number - generator Mersenne Twister, as used by GRand and GRandom. This was - necessary, because some seeds would yield very bad pseudo-random - streams. Further information can be found at: - - http://www.math.keio.ac.jp/~matumoto/emt.html - - Also the pseudo-random integers generated by g_rand_int_range and - g_random_int_range will have a slightly better equal distribution - with the new version of GLib. - - The original algorithms, as found in GLib-2.0.x, can be used instead - of the new ones by setting the environment variable G_RANDOM_VERSION - to the value of "2.0". - - Use the GLib-2.0 algorithms only if you have sequences of numbers - generated with Glib-2.0 that you need to reproduce exactly. +* GObject now enforces CONSTRUCT_ONLY properties; due to an oversight + in previous versions, it was possible to set CONSTRUCT_ONLY properties + after construct time. + +* The child watch functionality tends to reveal a bug in many + thread implementations (in particular the older LinuxThreads implementation + on Linux) where it's not possible to call waitpid() for a child + created in a different thread. For this reason, for maximum portability, + you should structure your code to fork all child processes that you want + to wait for from the main thread. + +* A problem was recently discovered with g_signal_connect_object(); + it doesn't actually disconnect the signal handler once the object being + connected to dies, just disables it. See the API docs for the function + for further details and the correct workaround that will continue to + work with future versions of GLib. How to report bugs ================== -- cgit v1.2.1