summaryrefslogtreecommitdiff
path: root/json-glib/json-builder.h
Commit message (Collapse)AuthorAgeFilesLines
* docs: Initial, rough port away from gtk-docEmmanuele Bassi2021-06-081-15/+0
| | | | | | | | | | Drop `SECTION` blurbs. Use gi-docgen syntax for internal links. Use summary lines for gi-docgen indices. Use Markdown syntax for code fragments.
* core: Add immutability support to core objectsPhilip Withnall2016-03-011-0/+2
| | | | | | | | | | | Add an immutable mode to JsonNode, JsonObject, JsonArray and JsonValue. This is an optional mode which objects enter by calling json_*_seal(). It is a one-way transition, which means that we can build and manipulate objects as much as desired, before sealing them and enjoying the benefits of immutable objects: no need to take copies when handling them, persistent hash values (still to be implemented). https://bugzilla.gnome.org/show_bug.cgi?id=756121
* Add autoptr macrosEmmanuele Bassi2016-02-291-0/+4
| | | | | | | GLib can take advantage of the "cleanup" attribute by using a bunch of macro magic. This has been slowly been used across various libraries in the G* stack, so JSON-GLib should provide symbols for the automatic memory management of its types.
* Use compiler annotations to determine symbol visibilityEmmanuele Bassi2014-03-181-0/+15
| | | | | | | | | | | | | | | | | Instead of relying on a separate file that requires being update every time we add a new public function we should use compiler annotations to let the linker know which symbols are public and exported. In order to achieve this we have to: * check for the visibility=hidden attribute * add -fvisibility=hidden to the linker flags * add a macro to annotate all public symbols While we're at it, we should copy the versioned symbols macro layout already used by GLib, GTK+, and other G* libraries, including the ability to express the range of allowed versions of JSON-GLib that third party code can compile against.
* docs: Port to MarkDownEmmanuele Bassi2014-03-181-4/+3
| | | | | Drop the DocBook documentation, and move everything to the MarkDown format used by modern gtk-doc.
* Move the single include guard after multiple inclusion oneEmmanuele Bassi2013-12-041-3/+3
| | | | | | | | | | | | | | GCC (and other compilers) can optimise multiple inclusion of headers if they find the: #ifndef FOO #define FOO #endif pattern as the first thing inside a header. The single-header inclusion guard was preventing that from happening, so we need to move it inside the multiple inclusion guard.
* builder: Add Since: annotationsEmmanuele Bassi2010-08-151-24/+30
|
* builder: Add convenience API for building JSON trees.Luca Bruno2010-06-161-0/+100
https://bugzilla.gnome.org/show_bug.cgi?id=621141 Signed-off-by: Emmanuele Bassi <ebassi@linux.intel.com>