mirror of
https://gitlab.gnome.org/GNOME/glib.git
synced 2025-01-23 12:41:50 +01:00
Low-level core library that forms the basis for projects such as GTK+ and GNOME.
397ad5881e
Fri May 5 01:15:48 2000 Tim Janik <timj@gtk.org>
* gtype.h: add reserved fundamental ids for gtk types (for transition
time). added G_TYPE_FUNDAMENTAL_MAX for gtk.
Mon Apr 17 20:45:50 2000 Tim Janik <timj@gtk.org>
* glib-gobject.c (g_object_base_class_finalize): oops, don't unset
n_params prior to destructing them.
Tue Apr 11 04:28:10 2000 Tim Janik <timj@gtk.org>
* fixed a couple of bugs in the initial parameter/object
implementations, after getting beast running on GObject and GValue.
Fri Apr 7 04:27:49 2000 Tim Janik <timj@gtk.org>
* glib-gobject.[hc]: completed parameter set/get implementations,
along with asyncronous parameter changed notification queue.
Sun Apr 2 04:54:36 2000 Tim Janik <timj@gtk.org>
* glib-gobject.[hc]: GObject implementation, that is facilities
for setting/getting quarked data and reference counting.
* glib-gparamspecs.[hc]: first actuall parameter implementations
for GLib, so far we have: char, uchar, bool, int, uint, long,
ulong, enum, flags, float, double, string and object. each of these
GParamSpecs is a new instantiatable type in its own respect,
so the .c file derives 13 new types from G_TYPE_PARAM and
defines over 50 (*2) conversion facilities.
* glib-gvaluecollector.h: generic varargs handling stubs for
GParamSpecs, private header file (does get installed for
inclusion into user code though).
* glib-gvalue.[hc]: GValue functionality implementation.
* glib-gparam.[hc]: basis GParamSpec implementation for
the virtual base type G_TYPE_PARAM.
* glib-genums.[hc]: enum/flags type implementation, based on
bseenum.[hc].
* glib-extra.[hc]: GLib additions, including 1.3 compatibility
routines and various other functions, from string manipulation
over list manipulation up to a unix signal GSource.
* glib-gtype.[hc]: GLib Type System implementation, heavily
based on BSE's dynamic type system.
|
||
|---|---|---|
| debian | ||
| docs | ||
| glib | ||
| gmodule | ||
| gobject | ||
| gthread | ||
| tests | ||
| .cvsignore | ||
| acconfig.h | ||
| acglib.m4 | ||
| acinclude.m4 | ||
| AUTHORS | ||
| autogen.sh | ||
| build-dll | ||
| 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.guess | ||
| config.h.win32.in | ||
| config.sub | ||
| configure.in | ||
| COPYING | ||
| garray.c | ||
| gasyncqueue.c | ||
| gbacktrace.c | ||
| gcache.c | ||
| gcompletion.c | ||
| gdataset.c | ||
| gdate.c | ||
| gerror.c | ||
| ghash.c | ||
| ghook.c | ||
| giochannel.c | ||
| giounix.c | ||
| giowin32.c | ||
| glib-config.in | ||
| glib.def | ||
| glib.h | ||
| glib.m4 | ||
| glib.rc.in | ||
| glib.spec.in | ||
| glibconfig.h.win32.in | ||
| glist.c | ||
| gmain.c | ||
| gmem.c | ||
| gmessages.c | ||
| gnode.c | ||
| gprimes.c | ||
| gqueue.c | ||
| grand.c | ||
| grel.c | ||
| gscanner.c | ||
| gslist.c | ||
| gstrfuncs.c | ||
| gstring.c | ||
| gthread.c | ||
| gthreadpool.c | ||
| gtimer.c | ||
| gtree.c | ||
| gutils.c | ||
| gwin32.c | ||
| HACKING | ||
| INSTALL | ||
| ltconfig | ||
| ltmain.sh | ||
| MAINTAINERS | ||
| Makefile.am | ||
| makefile.cygwin.in | ||
| makefile.msc.in | ||
| NEWS | ||
| README | ||
| README.win32 | ||
| sanity_check | ||
| testgdate.c | ||
| testgdateparser.c | ||
| testglib.c | ||
| TODO.xml | ||
*** IMPORTANT *** This is a development version of GLib. You should be using a stable version, which is available at ftp://ftp.gtk.org/pub/gtk/v1.2/. This version is meant for developers of GLib only: * You should not base stable software on this version of GLib. * GNOME developers should use a stable version of GLib. Distributions should *NOT* ship a development package of this GLib. Do not ship the headers and do not ship the glib-config script. These things will conflict with the stable 1.2 series. Package only enough to satisfy the requirements of some other package. Package only the library itself. Doing otherwise will do no favors to the community. If you install this version of GLib, we strongly recommend that you install it in a different prefix than GLib 1.2. Use --prefix as an argument to configure to do this. Otherwise, you will not be able to do development with GLib 1.2 any longer. *** You should be using GLib 1.2 instead. *** General Information =================== This is GLib version 1.3.1. GLib is a library which includes support routines for C such as lists, trees, hashes, memory allocation, and many other things. The official ftp site is: ftp://ftp.gtk.org/pub/gtk The official web site is: http://www.gtk.org/ A mailing list is located at: gtk-list@redhat.com To subscribe: mail -s subscribe gtk-list-request@redhat.com < /dev/null (Send mail to gtk-list-request@redhat.com with the subject "subscribe") Installation ============ See the file 'INSTALL' How to report bugs ================== To report a bug, send mail either to gtk-list, as mentioned above, or to gtk-bugs@gtk.org. If you send mail to gtk-list, you must be subscribed yourself. In the mail include: * The version of GLib * Information about your system. For instance: - What operating system and version - What version of X - 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 testglib program that is built in the glib/ directory, 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 can be uploaded to the incoming/ directory on ftp.gtk.org. Please follow the instructions there, and include your name and email address in the README file. If the patch fixes a bug, it is usually a good idea to include all the information described in "How to Report Bugs".