summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2010-10-08gthread-posix: Use PTHREAD_RWLOCK_PREFER_WRITER_NP if availablerwlockEdward Hervey1-1/+5
This is to emulate the same behaviour as the non-native rwlock
2010-10-08Initial native RWLock implementationEdward Hervey4-32/+169
2010-10-08add some test apps.Wim Taymans4-0/+151
2010-10-08use native pthread rwlocksWim Taymans2-0/+70
2010-10-08uhm, rename again, now it's consistentWim Taymans2-49/+49
2010-10-08gthread: rename functions to match static variantsWim Taymans1-33/+33
2010-10-08gthread: avoid locking in _get_mutex_implWim Taymans1-6/+17
When getting the mutex implementation of a static mutex, avoid taking the global lock every time but only take the lock when there was no mutex and we need to create one.
2010-10-08symbols: add new symbol tooWim Taymans1-0/+1
2010-10-08gthread: add GRWMutex prototypesWim Taymans2-0/+69
2010-10-08Initialise lengths in GvdbReader to silence warningsChristian Dywan1-1/+1
2010-10-08Initialise lengths in GDbusAuth to silence warningsChristian Dywan1-2/+2
2010-10-08Mention g_object_run_dispose correctly in tutorialChristian Dywan1-2/+2
Fixes: https://bugzilla.gnome.org/show_bug.cgi?id=630797
2010-10-07Updated British English translationBruce Cowan1-211/+258
2010-10-07Remove g_desktop_app_info_lookup_get_type symbol from gio.typesWilliam Jon McCann1-1/+0
It was removed in 9b262f1c5fe5a6fd879f17cd7b80d8c54e33d80c
2010-10-07Don't call close() on -1Tor Lillqvist1-1/+2
Of course, a proper implementation of close() will just ignore an invalid parameter silently, and set errno. But apparently the "debug" version of the Microsoft C library generates some noise in this case. So avoid that. Thanks to John Emmas for reporting.
2010-10-06Updated Hebrew translation.Yaron Shahrabani1-213/+236
2010-10-05Replace "gio-desktop-app-info-lookup" extension pointBastien Nocera4-127/+8
With a native version, that looks for desktop items supporting x-scheme-handler/foo, when looking for a handler for the "foo" URI scheme handler. https://bugzilla.gnome.org/show_bug.cgi?id=631410
2010-10-05volume monitor: don't unref NULLRyan Lortie1-2/+4
Fix a couple more cases of blindly calling g_object_unref() on the result of a function that is documented as sometimes returning NULL.
2010-10-05GVariant tests: fix bad allignment assumptionRyan Lortie1-5/+8
One of the GVariant test cases allocates a pair of character arrays on the stack and then passes them to functions that assume that they will be aligned to a multiple of two. This is not the case for some versions of GCC (4.0.3 on PowerPC).
2010-10-04GSettings test: fix error match stringsRyan Lortie1-4/+4
The name of the internal function that appears in an assertion message has changed. Update the tests.
2010-10-04gsettings-tool: Add 'range' subcommandRyan Lortie2-4/+67
Provides access to the g_settings_get_range() functionality, converting its return value to something that's reasonable for printing at the console and potentially parseable. The format may change. Bug #631264.
2010-10-04gsettings-tool: implement range-checkingRyan Lortie1-0/+7
Prevent assertion messages from spewing forth and also ensure that we exit with an error status in the event that the value was out of range. Bug #631264.
2010-10-04Update symbols and docs sectionsRyan Lortie2-1/+7
2010-10-04GSettings: add g_settings_range_check() APIRyan Lortie2-8/+46
Checks if a given value is within the correct range for a key.
2010-10-04Bug 631263 - GSettings needs range/choice APIsRyan Lortie4-1/+159
Add g_settings_get_range() to describe the possible values that may be provided to g_settings_set_value() without causing an error. Add a test case.
2010-10-04schema compiler: Don't store zero-valued flagsRyan Lortie1-1/+6
Don't store the "none" value for flags into the compiled schema file. "none" should never appear as a value -- no flags set is indicated by an empty array.
2010-10-04Bug 627126 - gsettings schemas on FreeBSDRyan Lortie1-14/+2
Rewrite the install rule for GSettings schemas to not depend on an obscure chunk of non-portable sed that nobody understands the purpose of. Instead, use make's VPATH feature to resolve the paths of the files that need to be installed. No need to depend on the .valid targets here since automake already ensures that 'make all' is complete before 'make install' is permitted to run.
2010-10-03glib-compile-schemas: write strinfo little endianRyan Lortie1-0/+6
Ensure that the strinfo is output in little-endian byte order on big endian machines. GSettings is now passing all of its tests on PowerPC. Bug #630968 is closed.
2010-10-03GSettings strinfo: byteswap integersRyan Lortie1-2/+2
strinfo is always strictly little endian, so ensure that we byteswap to native when comparing and returning.
2010-10-03GSettings endian: missed a spotRyan Lortie1-1/+1
Missed an instance of get_value -> get_raw_value search/replace.
2010-10-03GSettings big endian tweaksRyan Lortie2-11/+16
GSettings relies on parts of the schema infromation remaining unbyteswapped (the strinfo database, for example) while requiring other parts to be in native order (the default value, constraints, etc.). Lift the byteswapping into a place where we can do it selectively.
2010-10-03Merge remote branch 'gvdb/master'Ryan Lortie2-0/+26
2010-10-03Add gvdb_table_get_raw_value() API for GSettingsRyan Lortie2-0/+26
2010-10-03GSettings test: fix unsafe GObject properties useRyan Lortie1-6/+8
The test case was passing a guint16 to g_object_get() for a guint property. That's invalid on all systems, although it works (more or less) on little endian ones. On big endian it's a total no-go.
2010-10-03GVariant: avoid byteswapping in some casesRyan Lortie1-13/+27
Make g_variant_byteswap() merely return a new reference on the given value in the event that we know that byteswapping will have no effect (ie: types which have no alignment requirement). This fixes a somewhat complicated interaction between GVariant, GSettings and GVDB on big endian machines: GSettings assumes that it can unref values returned from GVDB without losing access to the underlying data. This only works if the underlying data is in the mapped file -- not a freshly-allocated buffer that GVariant byteswapped into.
2010-10-03Merge remote branch 'gvdb/master'Ryan Lortie2-6/+47
2010-10-03Fix reader on big endianRyan Lortie1-5/+5
Some of the hashtable code was failing to byteswap properly.
2010-10-03allow libtool 2.4Ryan Lortie1-1/+1
It's released now and it seems to work OK.
2010-10-03Bug 623400 - acquire context before dispatchingRyan Lortie3-72/+33
For GSettings. Use the functionality introduced in the last commit to simplify our notify dispatching and increase the safety of doing so (by ensuring that the context is acquired in the current thread for the duration of the dispatch). This closes bugs #623400 and #629849.
2010-10-03Bug 618737 - "dispatch to context" functionalityRyan Lortie3-0/+121
Adds a new function g_main_context_invoke() (and _full() variant). This function takes a main context, a function and a user_data. If the main context is already acquired in the current thread, the function is invoked directly. If the main context is the default main context of the current thread and it can be acquired then the function is invoked directly while the context is owned. Otherwise, the function is scheduled as an idle on the context.
2010-10-03Updated Lithuanian translation by Aurimas Černius <aurisc4@gmail.com>Žygimantas Beručka1-120/+158
2010-10-03gsettings-tool: RewriteRyan Lortie2-700/+405
Rewrite the GSettings tool. Improvements/changes: - simplify the code by performing common actions (like creating a schema) in only one place instead of one per-command - new features (list schemas, list keys, monitor multiple, etc) - factor-out bash completion and implement in shellscript - input validation: should never abort due to invalid inputs Still to do: - proper error checking for ranges/choices - support for querying range/choice information - bash completion support for enums Closes bug #629289, possibly among others.
2010-10-03GSettings: implement .property_get('path')Ryan Lortie1-0/+4
This was unimplemented in g_settings_get_property(), leading to a failed 'g_assert_not_reached()'.
2010-10-02Add 'Since:' tags for schema listing APIsRyan Lortie1-0/+4
2010-10-02Clean up g_settings_list_schemas()Ryan Lortie4-32/+103
In its previous form, g_settings_list_schemas() was not useful as a tool to prevent aborts due to using g_settings_new() with an invalid schema name. This is because g_settings_list_scheams() also listed relocatable schemas, and calling g_settings_new() for those would abort just the same as if you called it for a non-existent schema. Modify g_settings_list_schemas() so that it only returns schemas for which it is safe to call g_settings_new(). Add another call for sake of completeness: g_settings_list_relocatable_schemas().
2010-10-02Updated Bulgarian translationDamyan Ivanov1-48/+95
2010-10-01Improve .gitignoreRyan Lortie1-0/+1
2010-10-01Bug 628937 - gracefully handle broken schemasRyan Lortie1-38/+83
Implement the second feature requested in the bug: silently ignore override files that attempt to override schemas that are not currently installed. Also, support 'strictness' being optional for other errors when parsing override files (ie: inability to open the file, unknown key name, parse errors, out of range). We don't completely back out the file in this case — as that is difficult with the current implementation — but just ignore the override for the single key.
2010-10-01glib-compile-schemas: improve error accuracyRyan Lortie1-3/+4
We wrote "<enum> must contain at least one <value>" for empty <flags>. Fix that.
2010-10-01Bug 628937 - gracefully handle broken schemasRyan Lortie2-18/+72
Implement the first of two features requested in the bug: when encountering a broken .xml schema file, back out the changes in that file and continue to parse other files. This prevents a single broken .xml file from messing up GSettings for everyone else. Add a --strict option to get the old behaviour. Use this from the test cases.