[glib] GObject: Clarify 8db5542803 by avoiding double -ve
- From: Daniel Boles <dboles src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [glib] GObject: Clarify 8db5542803 by avoiding double -ve
- Date: Sun, 22 Apr 2018 14:07:45 +0000 (UTC)
commit 042ab215b2aba5f132d4abac40495ac7da9579fb
Author: Daniel Boles <dboles src gnome org>
Date: Sun Apr 22 15:03:03 2018 +0100
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!
gobject/gobject.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
---
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
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]