Gio.Initable

const Gio = imports.gi.Gio;

let initable = new Gio.Initable();
  

Gio.Initable is implemented by objects that can fail during initialization. If an object implements this interface then it must be initialized as the first thing after construction, either via Gio.Initable.prototype.init or Gio.AsyncInitable.prototype.init_async (the latter is only available if it also implements Gio.AsyncInitable).

If the object is not initialized, or initialization returns with an error, then all operations on the object except GObject.Object.prototype.ref and GObject.Object.prototype.unref are considered to be invalid, and have undefined behaviour. They will often fail with g_critical() or g_warning(), but this must not be relied on.

Users of objects implementing this are not intended to use the interface method directly, instead it will be used automatically in various ways. For C applications you generally just call Gio.Initable.new directly, or indirectly via a foo_thing_new() wrapper. This will call Gio.Initable.prototype.init under the cover, returning null and setting a GLib.Error on failure (at which point the instance is unreferenced).

For bindings in languages where the native constructor supports exceptions the binding could check for objects implemention %GInitable during normal construction and automatically initialize them, throwing an exception on failure.

Since 2.22

Prerequisites

Initable requires GObject.Object

Known Implementations

Initable is implemented by CharsetConverter, DBusConnection, DBusObjectManagerClient, DBusProxy, DBusServer, InetAddressMask, Socket and Subprocess