| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| |
| |
| |
| | |
This fixes deserialization to match serialization (bug 648539)
|
| |
| |
| |
| | |
deserialized.
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
These are the VS 2010 project files to build JSON-GLib
and its test programs. The project for building the main JSON-GLib
DLL has its source files input into it by the preprocessor during
"make dist", like the VS2008 project files, simplifying its maintenance.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Add automation support for config.h.win32(.in), so config.h.win32
will be distributed with the correct version info during "make dist"
Also eliminate json-version.h.win32 as it is no longer needed (distribute
json-version.h during "make dist")
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This updates the autotools files so that the project to compile the main
JSON-GLib DLL will have its source files filed into the project during
"make dist". Plus, it enables the creation/distribution of json-version.h
and config.h.win32 with the correct version info during "make dist".
These changes will simplify the maintenance of the VS project files,
and support for VS2010 is also added here, with similar automation support,
too.
|
|/
|
|
|
|
| |
Add automation support for the VS 2008 project files
These are the updated VS 2008 Project files and property sheets
themselves. x64 compiling support is also added
|
|
|
|
| |
JSON-GLib uses the GNOME Bugzilla instance.
|
|
|
|
| |
Building against JSON-GLib requires GIO.
|
|
|
|
| |
Instead of manual iteration, let's use the function GList provides us.
|
|
|
|
|
|
| |
Since we check for the contents of the $host variable to detect
compilation on/for win32, we should also be using the canonicalization
facilities from autoconf.
|
|
|
|
|
|
|
|
| |
Some small internal change from passing the signature to a pointer to
the signature down the call chain caused all the checks for
signature==NULL to fail.
Signed-off-by: Emmanuele Bassi <ebassi@linux.intel.com>
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=640729
|
| |
|
|
|
|
|
| |
Verify that setting an object member multiple times does not lead to
random values.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When calling g_hash_table_replace() we also free the string holding the
member name. This means that the const gchar* pointer we store inside
the list of ordered member names now points to garbage - so if somebody
tries to iterate over the members list it will get random values instead
of a valid C string.
Since we guaranteed insertion order, if we replace the contents of a
JsonObject member we need to find the right pointer and replace it: just
removing and prepending won't do.
https://bugzilla.gnome.org/show_bug.cgi?id=642383
|
|
|
|
|
|
| |
Free the current_member string, and since we're destroying data we own
let's do it inside the finalize implementation instead of the dispose
one.
|
|
|
|
| |
This should allow easy access to the member name during iteration.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If we assume that a JSON object is just an array with a named mapping
then the JsonReader API should be able to descend into objects using the
same API used for arrays.
This obviously is less useful than it sounds if we take a very strict
interpretation of JSON objects as unordered string-to-value mappings; as
the ordering is not guaranteed to be stable, parsers would be fairly
weak against various JSON definitions.
If the JSON format parsed is guaranteed to be stable then an integer
offset might be an easy (albeit slightly less performant) way to access
data.
|
|
|
|
|
| |
Allow retrieving a list of member names from the current cursor position
of the JsonReader. It's useful if you're trying to inspect a JSON tree.
|
|
|
|
|
|
|
|
|
| |
G_VARIANT_CLASS_DICTIONARY is a define; GCC complais loudly when trying
to use a switch() on an enumeration type with case values not from the
enumeration.
Plus: coding style in JSON-GLib is mostly the same as GTK+ and Clutter,
so we should adhere to it.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=632940
|
|
|
|
|
|
| |
Use only bzip2, since it gives better compression ratios; the
installation script on gnome.org will create a gzipped tarball by itself
anyway.
|
| |
|
|
|
|
|
|
|
|
|
| |
Integrate the files inside the build, though it's still not fully
automated.
https://bugzilla.gnome.org/show_bug.cgi?id=635484
Signed-off-by: Emmanuele Bassi <ebassi@linux.intel.com>
|
| |
|
|
|
|
| |
Bug #635398
|
|
|
|
| |
Check if we're setting the same node, to avoid a needless replace.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=638932
|
|
|
|
|
|
|
| |
The nice format escape for g_ascii_formatd() is not really suited for a
serialization format, as it obviously loses precision.
https://bugzilla.gnome.org/show_bug.cgi?id=637244
|
|
|
|
|
| |
Serialization of floating point values might lead to odd formats,
especially when dealing with IEEE machine-neutral values.
|
|
|
|
| |
Use modern API to deal with properties installation and notification.
|
|
|
|
|
|
|
|
| |
Instead of asking everyone to use g_object_set() to set up a
JsonGenerator the class should provide a decent API for its properties.
While we're at it, we should also use modern API for installing and
notifying of property changes.
|
|
|
|
|
|
| |
There shouldn't be a requirement for this, since we're using the GLib
function explicitely for this reason, but it's always good to have a
comprehensive test suite.
|
|
|
|
|
| |
JsonGenerator is not able to generate strings for bare values, something
that completely went under the radar for all this time.
|
|
|
|
|
| |
Upstream GLib fixed the test rules to avoid repeating the test suite
three times.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Commit 2d7550948dfb2e5907b851bc2c4bd296a7526086 broke the construct-only
properties; we now only check for the G_PARAM_CONSTRUCT_ONLY flag, and
pass construct-only properties to g_object_newv(); all the properties
flagged as G_PARAM_CONSTRUCT gets passed with the rest of the properties
after that.
|
|
|
|
|
| |
If you don't override JsonSerializable, you get the default behaviour
anyway.
|
| |
|
| |
|
|
|
|
|
|
| |
Add --warn-all for the scanner flags.
Also, undefine JSON_DISABLE_DEPRECATED, to introspect deprecated API.
|
| |
|