Don't keep the lists of source files for libglib, libgobject and
libgio in the VS project files in addition to the canonical location,
the corresponding Makefile.am files.
Instead, generate the corresponding .vcproj files at make dist time
using the C preprocessor, from template files called .vcprojin. We
still list explicitly in the .vcprojin files some of the
Windows-specific source files, and the sources files of gnulib and
pcre.
NaN floating point values get mangled when passing across the function
call ABI on x86 so avoid using them to get rid of spurious failures.
Reported by Christian Persch and reliably reproduced by Emilio Pozuelo
Monfort.
Use g_io_add_watch(), g_io_add_watch_full() and
g_source_remove() instead the deprecated gtk_input_add_full(),
gtk_input_remove(), gdk_input_add(), gdk_input_add_full() and
gdk_input_remove()
Merge GVariant variable arguments support and put it under tests.
Also, remove the hack of the test case directly '#include'ing .c files
from glib/. Instead, create a non-installed gvariant-internal.h that
the tests can include and make the symbols in it visible on the symbol
table of the shared library. These symbols (as they are present in no
installed header files) are not part of the API of GLib.
Increase test coverage in a few other areas.
Remove the macros for the g_malloc_n family -- calls directly to those
functions now always go directly to those functions.
Reimplement the macros for g_new and friends.
Remove the branch that checked for calling g_new() with a constant
n_structs == 1. With the struct size always known this case will now be
caught under the case that does the inline multiplication and the
multiplication by 1 will be optimised away.
Don't check that a GVariantBuilder is fully-valid for use when
performing refcounting operations, as these operations may be occuring
after the builder has already been cleared.
Issue caught by Michael Meeks. This patch based on his.
GVariantTypeInfo was dropping the reference count on the TypeInfo
structure before removing it from the hash table. This means that
another thread could come along and grab the value from the hash table
in the meantime.
Solve this by holding the lock on the table before dropping the
reference.
Also: move the hash table initialisation inside of the lock to remove
the standard double-initialisation race plus a more insidious issue
caused by the fact that we free the hash table once it becomes empty.
