mirror of
https://gitlab.gnome.org/GNOME/glib.git
synced 2024-12-25 15:06:14 +01:00
Low-level core library that forms the basis for projects such as GTK+ and GNOME.
f4d7817b13
Wed Mar 27 18:42:22 2002 Tim Janik <timj@gtk.org> * gmessages.[hc]: major cleanups. introduced _g_log_fallback_handler() to handle recursive messages which really doesn't call any GLib functions. this allowes the default handler to use normal GLib functions and also fixes user supplied log level handlers. fixed locking issues, based on a patch from Sebastian Willhelmi, attached to #74356. translate log messages from UTF-8, based on the same patch. save fatal and recursion flags across flag loop. use new integer format code from above patch. move GLib functions out of locked mutex state to avoid deadlocks. move the level prefix and filedescriptor logic into mklevel_prefix(). move _g_debug_init() into a place where we can figure and handle recursion. |
||
---|---|---|
debian | ||
docs | ||
glib | ||
gmodule | ||
gobject | ||
gthread | ||
m4macros | ||
po | ||
tests | ||
.cvsignore | ||
acconfig.h | ||
acglib.m4 | ||
acinclude.m4 | ||
AUTHORS | ||
autogen.sh | ||
ChangeLog | ||
ChangeLog.pre-1-2 | ||
ChangeLog.pre-2-0 | ||
ChangeLog.pre-2-2 | ||
ChangeLog.pre-2-4 | ||
ChangeLog.pre-2-6 | ||
ChangeLog.pre-2-8 | ||
ChangeLog.pre-2-10 | ||
ChangeLog.pre-2-12 | ||
config.h.win32.in | ||
configure.in | ||
COPYING | ||
glib-2.0-uninstalled.pc.in | ||
glib-2.0.pc.in | ||
glib-gettextize.in | ||
glib-zip.in | ||
glib.spec.in | ||
glibconfig.h.win32.in | ||
gmodule-2.0-uninstalled.pc.in | ||
gmodule-2.0.pc.in | ||
gobject-2.0-uninstalled.pc.in | ||
gobject-2.0.pc.in | ||
gthread-2.0-uninstalled.pc.in | ||
gthread-2.0.pc.in | ||
HACKING | ||
INSTALL | ||
INSTALL.in | ||
Makefile.am | ||
makefile.mingw | ||
makefile.msc | ||
msvc_recommended_pragmas.h | ||
NEWS | ||
NEWS.pre-1-3 | ||
README | ||
README.in | ||
README.win32 | ||
sanity_check | ||
TODO.xml | ||
win32-fixup.pl |
General Information =================== This is GLib version 2.0.0. 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 ftp site is: ftp://ftp.gtk.org/pub/gtk The official web site is: http://www.gtk.org/ Information about mailing lists can be found at http://www.gtk.org/mailinglists.html To subscribe: mail -s subscribe gtk-list-request@gnome.org < /dev/null (Send mail to gtk-list-request@gnome.org with the subject "subscribe") Installation ============ See the file 'INSTALL' Notes about GLib-2.0.0 ====================== * On systems without the libintl from GNU gettext() or a recent version of the GNU C library, the encoding of translated error messages will be incorrect (they should be in UTF-8). A workaround for this is to install GNU gettext and use that libintl. This is expected to be fixed in GLib-2.0.1. Application programmers should not call g_locale_to_utf8() on these strings. * Similarly, the GLib error logging functions such as g_print(), g_warning(), g_error(), currently do not convert the strings they are passed from UTF-8 to the encoding of the locale, or check that the strings they are passed are valid UTF-8. They should, despite this, be assumed to take UTF-8 arguments. How to report bugs ================== Bugs should be reported to the GNOME bug tracking system. (http://bugzilla.gnome.org, product glib.) You will need to create an account for yourself. In the bug report 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 the testgtk program that is built in the gtk/ 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 occured. * Further information such as stack traces may be useful, but is not necessary. Patches ======= Patches should also be submitted to bugzilla.gnome.org. If the patch fixes an existing bug, add the patch as an attachment to that bug report. Otherwise, enter a new bug report that describes the patch, and attach the patch to that bug report. Bug reports containing patches should include the PATCH keyword in their keyword fields. If the patch adds to or changes the GLib programming interface, the API keyword should also be included. Patches should be in unified diff form. (The -u option to GNU diff.)