summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDaniel Boles <dboles@src.gnome.org>2018-04-22 15:03:03 +0100
committerDaniel Boles <dboles@src.gnome.org>2018-04-22 15:03:03 +0100
commit042ab215b2aba5f132d4abac40495ac7da9579fb (patch)
tree9a03b831efa68416659596df0858c17be1362340
parentcf581713426871cbd764a594f92aae0f7491f961 (diff)
downloadglib-042ab215b2aba5f132d4abac40495ac7da9579fb.tar.gz
GObject: Clarify 8db5542803 by avoiding double -ve
Make the wording easier to understand by saying what we do, rather than what we avoid doing if the relevant thing did not happen!
-rw-r--r--gobject/gobject.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/gobject/gobject.c b/gobject/gobject.c
index cef98b7f7..555ca3fae 100644
--- a/gobject/gobject.c
+++ b/gobject/gobject.c
@@ -487,7 +487,7 @@ g_object_do_class_init (GObjectClass *class)
* in ::notify being emitted, even if the new value is the same as the old.
* If they did pass %G_PARAM_EXPLICIT_NOTIFY, then this signal is emitted only
* when they explicitly call g_object_notify() or g_object_notify_by_pspec(),
- * and common practice is to avoid doing so if the value remained unchanged.
+ * and common practice is to do that only when the value has actually changed.
*
* This signal is typically used to obtain change notification for a
* single property, by specifying the property name as a detail in the