mirror of
https://gitlab.gnome.org/GNOME/glib.git
synced 2025-03-28 10:30:03 +01:00
448e792b0a
Sat Jan 23 22:45:59 1999 Jeff Garzik <jgarzik@pobox.com>
* ghash.c (g_hash_table_lookup_node, g_hash_table_lookup,
g_hash_table_insert, g_hash_table_remove,
g_hash_table_lookup_extended):
- Fixed bug that overwrote nodes in hash buckets instead of
adding them to the hash bucket node list.
Hash tables now work as advertised.
(g_hash_table_resize):
- Use g_new0 instead of manual init.
- Space out code a bit for readability.
(g_hash_nodes_destroy):
- Replaced "if (!hash_node) return;" with
"if (hash_node) {do stuff}".
Testing takes up less code space than explicit call to
'return' before end of function. (look at gcc -S)
Updated module header copyright to 1999.
New module macro G_HASH_BUCKET for (table,key)->bucket lookups.
* tests/hash-test.c:
- Add two new tests, one with strings as the keys and values, and
one with ints as the keys and values. Tests indirect (strings)
and direct (ints) hashing.
- Cleanup unused junk left over from testglib.c.
- Converted a g_print call to g_assert_not_reached.
- Updated copyright to 1999.
* testglib.c, tests/string-test.c:
- Init 'tmp_string' var to NULL, silencing uninit-var warning.
General Information =================== This is GLib version 1.1.13. GLib, is a library which includes support routines for C such as lists, trees, hashes, memory allocation, and many other things. Versions of GLib prior to 1.1.0 are distributed with GTK+ versions prior to 1.1.0. 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".