diff options
| author | Daniel Boles <dboles@src.gnome.org> | 2018-05-20 16:16:05 +0100 |
|---|---|---|
| committer | Daniel Boles <dboles.src@gmail.com> | 2018-05-20 16:38:35 +0100 |
| commit | 7d8b778aae95e8cf425ea040fa370caf3c6b9ebb (patch) | |
| tree | c7d4b537d522e62455dddbd9cb316e9395c99c7b | |
| parent | b2461f9e1b9aaf02f16a27d49f43abe1ce84b900 (diff) | |
| download | glibmm-2-54.tar.gz | |
AsyncResult: Bin obsolete docs re: initing GThreadglibmm-2-54
As the GLib Threads documentation states:
“Since version 2.32, the GLib threading system is automatically
initialized at the start of your program, and all thread-creation
functions and synchronization primitives are available right away.”
| -rw-r--r-- | gio/src/asyncresult.hg | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/gio/src/asyncresult.hg b/gio/src/asyncresult.hg index 10a80c60..7795deb6 100644 --- a/gio/src/asyncresult.hg +++ b/gio/src/asyncresult.hg @@ -94,9 +94,6 @@ using SlotAsyncReady = sigc::slot<void, Glib::RefPtr<AsyncResult>&>; * The callback for an asynchronous operation is called only once, and is always called, even in the case of a cancelled operation. * On cancellation the result is a ERROR_CANCELLED error. * - * Some ascynchronous operations are implemented using synchronous calls. These are run in a separate GThread, but otherwise they are sent - * to the Main Event Loop and processed in an idle function. So, if you truly need asynchronous operations, make sure to initialize GThread. - * * @newin{2,16} */ class AsyncResult : public Glib::Interface |