summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2011-12-08Add test for GDBusConnection singleton access racing with destructiongweakref-rwlock-548954Simon McVittie1-0/+128
Bug: https://bugzilla.gnome.org/show_bug.cgi?id=665211
2011-12-08GDBusConnection: use GWeakRef to make the singletons thread-safeSimon McVittie1-24/+16
Bug: https://bugzilla.gnome.org/show_bug.cgi?id=665211
2011-12-08Add regression test for GWeakRef used to cache a singletonSimon McVittie1-0/+121
Bug: https://bugzilla.gnome.org/show_bug.cgi?id=548954
2011-12-08Add deterministic tests for the API of GWeakRefSimon McVittie1-0/+108
These don't address the thread-safety, but do address basic use. Bug: https://bugzilla.gnome.org/show_bug.cgi?id=548954
2011-12-08GWeakRef: add a weak GObject reference believed to be thread-safeSimon McVittie3-2/+288
Heavily based on an implementation by Ryan Lortie, but with various API changes. Bug: https://bugzilla.gnome.org/show_bug.cgi?id=548954
2011-12-08g_object_weak_ref, g_object_add_weak_pointer: document non-thread-safetySimon McVittie1-0/+9
Transparent access to a weak pointer from the thread performing the weak -> strong conversion is incompatible with thread-safety: that thread will have to do something special. This is GNOME#548954. Bug: https://bugzilla.gnome.org/show_bug.cgi?id=548954
2011-12-08GBitLock: turn assumptions of g_futex_int_address into a static assertionSimon McVittie1-0/+6
We'll probably never encounter a platform where these fail, but that's what static assertions are for...
2011-12-07UpdatesMatthias Clasen1-0/+45
2011-12-07Clarify docs around main loop vfuncsMatthias Clasen2-7/+9
Mention that the vfuncs are no longer used, and tweak the wording around what g_application_run() does. https://bugzilla.gnome.org/show_bug.cgi?id=665391
2011-12-07Bug 665733 – GDBusConnection holds lock while calling destroynotifyDavid Zeuthen2-28/+21
Fix this problem by always running the destroynotify from an idle. https://bugzilla.gnome.org/show_bug.cgi?id=665733 Signed-off-by: David Zeuthen <davidz@redhat.com>
2011-12-06unicode: Fix a few issues with G_UNICHAR_MAX_DECOMPOSITION_LENGTHPhilip Withnall4-5/+7
Raised by Matthias in bgo#665685 but which I didn't spot until after pushing commit 3ac7c35656649b1d1fcf2ccaa670b854809d4cd8. Renames G_UNICHAR_MAX_DECOMPOSITION_LEN to G_UNICHAR_MAX_DECOMPOSITION_LENGTH and fixes a few documentation issues. See: bgo#665685
2011-12-06Bug 665685 — Add a #define for the max length of a Unicode decompositionPhilip Withnall3-4/+16
Add G_UNICHAR_MAX_DECOMPOSITION_LEN for the maximum length of the decomposition of a single Unicode character. Closes: bgo#665685
2011-12-06GDBus: Note in docs that g_dbus_node_info_new_for_xml() is using GMarkupDavid Zeuthen1-0/+4
This was discussed in bug 665634. https://bugzilla.gnome.org/show_bug.cgi?id=665634 Signed-off-by: David Zeuthen <davidz@redhat.com>
2011-12-06GDBus: fix link to D-Bus specDavid Zeuthen1-1/+1
Signed-off-by: David Zeuthen <davidz@redhat.com>
2011-12-06Minor doc fix.Behdad Esfahbod1-1/+1
2011-12-06MinorBehdad Esfahbod1-1/+1
2011-12-06Make the qsort_r check cross-compile friendlyMatthias Clasen1-1/+1
Pointed out by Daniel Mack. https://bugzilla.gnome.org/show_bug.cgi?id=665607
2011-12-05outputstream: Clarify docs of flush()Benjamin Otte1-3/+5
After questioning the semantics of flush on IRC, it seemed necessary to clarify what flushing is supposed to do. The Linux man page for fflush() seemed to cover it perfectly, so I just copied it. I did not add the "via the underlying write mechanism" part as that in my opinion is not something subclasses should need to guarantee.
2011-12-05Send CHANGES_DONE_HINT on file moves if no IN_CLOSE_WRITE is emittedCosimo Alfarano3-1/+35
This patch makes GFileMonitor to emit EVENT_CHANGES_DONE_HINT when EVENT_CREATED is emitted but the file is not opened for writing. On file moves across different mounted volumes, inotify will always emit IN_CREATE and IN_CLOSE_WRITE (plus other events). This translates into GIO's _EVENT_CREATED and _EVENT_CHANGES_DONE_HINT. On file moves across the same mounted volumes, inotify will emit IN_MOVED_FROM/IN_MOVED_TO which will be translated into _EVENT_DELETED/_EVENT_CREATED GIO's side. No _EVENT_CHANGES_DONE_HINT is emited afterwards. Under such circumstances a file indexer does not know when actually the file is ready to be indexed, either waiting too much or triggering the indexing twice. On small devices it's not advisable. Bug: https://bugzilla.gnome.org/show_bug.cgi?id=640077 Bug-NB: NB#219982 Reviewed-by: Simon McVittie <simon.mcvittie@collabora.co.uk> Reviewed-by: Tomas Bzatek <tbzatek@redhat.com>
2011-12-05GDBusConnection: propagate error correctly if flags are inappropriateSimon McVittie1-1/+1
Previously, this would fail the assertion "connection->initialization_error != NULL" after the label "out". Bug: https://bugzilla.gnome.org/show_bug.cgi?id=665067 Signed-off-by: Simon McVittie <simon.mcvittie@collabora.co.uk> Reviewed-by: David Zeuthen <davidz@redhat.com>
2011-12-02Link to libpcre correctly when static linkingSam Thursfield1-0/+1
https://bugzilla.gnome.org/show_bug.cgi?id=665298
2011-12-02Updated Spanish translationDaniel Mustieles1-105/+98
2011-12-02GDBusInterfaceSkeleton: make it possible to export on multiple connectionsTristan Van Berkom7-87/+592
This is useful in peer-to-peer connections. With minor changes by David Zeuthen <davidz@redhat.com>. https://bugzilla.gnome.org/show_bug.cgi?id=662718 Signed-off-by: David Zeuthen <davidz@redhat.com>
2011-12-02GVariant: add preconditions to ref. counting functionsPhilip Withnall1-0/+10
These prevent GVariants from accidentally being brought back to life after being freed, and should make it easier to track down ref. counting issues. Closes: bgo#665184
2011-12-01Updated Norwegian bokmål translationKjartan Maraas1-43/+33
2011-12-01GMemoryInputStream/GMemoryOutputStream: fix bug in previous commitDan Winship3-8/+86
A g_input_stream_read_async() implementation can't call g_input_stream_read() on itself directly because it will fail because the pending flag is already set. So fix that by invoking the vmethod directly rather than calling the wrapper. Likewise with GMemoryOutputStream. Add a test to gio/tests/memory-input-stream.c to catch read_async failures in the future.
2011-11-30GMemoryInputStream/GMemoryOutputStream: make these properly subclassableDan Winship2-7/+7
The async methods were directly invoking their own implementations of the sync methods, making it impossible for a subclass to reimplement them. https://bugzilla.gnome.org/show_bug.cgi?id=664635
2011-11-29Don't abort if g_ascii_strtod tests failMatthias Clasen1-23/+2
https://bugzilla.gnome.org/show_bug.cgi?id=652560
2011-11-29Remove two useless lines of codeGeek871-2/+0
https://bugzilla.gnome.org/show_bug.cgi?id=648516
2011-11-29Fix a little comment error in the _GTreeNode structGeek871-1/+1
https://bugzilla.gnome.org/show_bug.cgi?id=648516
2011-11-29Clarify local_command_line docsMatthias Clasen1-3/+4
https://bugzilla.gnome.org/show_bug.cgi?id=641720
2011-11-29Do not use static GTypeInfo and GInterfaceInfoNicola Fontana21-29/+29
Either g_type_register_static_simple (used by G_DEFINE_TYPE_EXTENDED) and G_IMPLEMENT_INTERFACE use automatic variables for GTypeInfo and GInterfaceInfo structs, while tutorials and source code often use static variables. This commit consistently adopts the former method. https://bugzilla.gnome.org/show_bug.cgi?id=600161
2011-11-29gnetworkmonitornetlink.c: Make the error messages less geekyDan Winship1-5/+5
This makes several different errors have identical messages, but they're pretty much "can't happen" situations anyway. https://bugzilla.gnome.org/show_bug.cgi?id=664406
2011-11-29gzlibdecompressor.c: fix a commentDan Winship1-1/+1
2011-11-29Add missing annotation to g_file_set_attribute()Michael Vogt1-2/+2
g_file_set_attribute() also permits a NULL value for value_p, and requires it to be NULL to unset it. Also fix the wrong variable name in the documentation. Signed-off-by: Martin Pitt <martin.pitt@ubuntu.com>
2011-11-28Forgot one interface...Matthias Clasen1-3/+24
2011-11-28Use an XML blob for gapplication interface infoMatthias Clasen1-107/+58
This is both more readable and more efficient. Double win !
2011-11-27gtester: Add command line option to skip testsCarlos Garcia Campos3-0/+42
https://bugzilla.gnome.org/show_bug.cgi?id=664809
2011-11-26Rearrange GApplication docsMatthias Clasen1-2/+2
Move the GApplication docs to the front of the section, where they belong.
2011-11-26gio.symbols: add g_application_[gs]et_default()Ryan Lortie1-0/+2
2011-11-26CosmeticsMatthias Clasen1-3/+3
Reword the title of GSimpleAction in the docs.
2011-11-26GApplication: add default applicationRyan Lortie2-0/+52
2011-11-26GApplication: unregister action interface exportRyan Lortie1-0/+6
We missed a few cases of unexporting the action group interface (in error cases, and on GApplication teardown).
2011-11-26GApplication: Implement query_actionMatthias Clasen1-106/+32
2011-11-26GSimpleActionGroup: Implement query_actionMatthias Clasen1-74/+20
2011-11-26Add g_action_group_query_action()Ryan Lortie4-5/+204
This new API allows requesting multiple pieces of information about a particular action in one go and also simplifies the burden for GActionGroup implementations -- they need not implement all the separate APIs now.
2011-11-24GBytes: A new type for an immutable set of bytes.Stef Walter25-371/+1102
* Represents an immutable reference counted block of memory. * This is basically the internal glib GBuffer structure exposed, renamed, and with some additional capabilities. * The GBytes name comes from python3's immutable 'bytes' type * GBytes can be safely used as keys in hash tables, and have functions for doing so: g_bytes_hash, g_bytes_equal * GByteArray is a mutable form of GBytes, and vice versa. There are functions for converting from one to the other efficiently: g_bytes_unref_to_array() and g_byte_array_free_to_bytes() * Adds g_byte_array_new_take() to support above functions https://bugzilla.gnome.org/show_bug.cgi?id=663291
2011-11-23Fix distcheckMatthias Clasen4-4/+4
Now that we have switched to template-free docs, these hand-rolled cleanup rules get in the way.
2011-11-23GInitable, GAsyncInitable: not initializing gives undefined behaviourSimon McVittie2-14/+25
This is the ISO C sense of undefined behaviour, in which works-by-coincidence, critical warning, abort, demons-fly-out-of-your-nose are all valid implementations. Bug: https://bugzilla.gnome.org/show_bug.cgi?id=662208 Signed-off-by: Simon McVittie <simon.mcvittie@collabora.co.uk> Reviewed-by: David Zeuthen <davidz@redhat.com>
2011-11-23GDBusWorker: continue_writing: initialize flush_async_data if closingSimon McVittie1-5/+3
This was a regression in commit f41178c6c: flush_async_data wasn't necessarily NULL in the "don't flush" case. Also move initialization of these variables up so that it's unconditional, since that's easier to verify than checking that each branch gets it right. Bug: https://bugzilla.gnome.org/show_bug.cgi?id=664617 Signed-off-by: Simon McVittie <simon.mcvittie@collabora.co.uk>
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-09 19:44:24 +0000