mirror of
https://gitlab.gnome.org/GNOME/glib.git
synced 2025-02-24 19:22:11 +01:00
d9f1357113
1999-03-15 Sebastian Wilhelmi <wilhelmi@ira.uka.de> * configure.in: Added the macros G_(U)?INT_(8|16|32|64)_FORMAT to use for printf and (much more important) scanf format strings for the corresponding GLib types. * glib.h Added G_(U)?(SHORT|INT|LONG)_FORMAT for consistency. It however makes no sense to also provide G_(FLOAT|DOUBLE)_FORMAT, as they are different for printf (f for both) and scanf (f for float, lf for double). Defining G_INT_FORMAT makes sense however, as we might want to define gint to something different than int someday in the future. Idea from Sascha Brawer <sb@adasys.ch>.
General Information =================== This is GLib version 1.2.0. 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".