| commit | ac42183c33b6dbb05c9c9af52fcacb2805ddb3b6 | |
| author | Emmanuele Bassi <ebassi@gnome.org> | |
| Tue, 27 Mar 2018 15:46:55 +0000 (27 16:46 +0100) | ||
| committer | Emmanuele Bassi <ebassi@gnome.org> | |
| Wed, 28 Mar 2018 10:49:59 +0000 (28 11:49 +0100) | ||
| tree | 055a60eee938090f9c33c5c0b60133ad404fa3f6 | treesnapshot (tar.gz zip) |
| parent | dd8d33d9681da222c06fd8cf39dd073a5333e076 | commitdiff |
Initialize variable
The `mount_monitor` variable is only set if the boolean
`with_mount_monitor` variable is set to TRUE, but the compiler does not
know that, so it'll warn when calling `g_clear_object()` even if the
clearing operation is gated with the same boolean.
Initializing with NULL does not cost us anything, and eliminates a
conditional branch.
https://bugzilla.gnome.org/show_bug.cgi?id=794732
The `mount_monitor` variable is only set if the boolean
`with_mount_monitor` variable is set to TRUE, but the compiler does not
know that, so it'll warn when calling `g_clear_object()` even if the
clearing operation is gated with the same boolean.
Initializing with NULL does not cost us anything, and eliminates a
conditional branch.
https://bugzilla.gnome.org/show_bug.cgi?id=794732
| gio/tests/g-file-info-filesystem-readonly.c | diffblobblamehistory |