summaryrefslogtreecommitdiff
path: root/gtk/gtkliststore.c
diff options
context:
space:
mode:
authorMatthias Clasen <mclasen@redhat.com>2020-09-12 12:01:04 -0400
committerMatthias Clasen <mclasen@redhat.com>2020-09-12 12:01:04 -0400
commit929a56e53cddb56e9057ff6c3aa2d968ce31a103 (patch)
tree65742eabdc7437b5c8a8712b3cc64b27e56ab94d /gtk/gtkliststore.c
parent6ed1c181eeb5c59915300eea821b8008c18f25b3 (diff)
downloadgtk+-929a56e53cddb56e9057ff6c3aa2d968ce31a103.tar.gz
Clean up lots of GTK+ -> GTK
Replace most remaining uses of GTK+ in the docs and user-visible strings by GTK. Also remove some leftover "Was added in 3.x" sentences from the docs.
Diffstat (limited to 'gtk/gtkliststore.c')
-rw-r--r--gtk/gtkliststore.c14
1 files changed, 7 insertions, 7 deletions
diff --git a/gtk/gtkliststore.c b/gtk/gtkliststore.c
index fa5fdc725a..f5b1347fbe 100644
--- a/gtk/gtkliststore.c
+++ b/gtk/gtkliststore.c
@@ -106,13 +106,13 @@
*
* # Performance Considerations
*
- * Internally, the #GtkListStore was implemented with a linked list with
- * a tail pointer prior to GTK+ 2.6. As a result, it was fast at data
- * insertion and deletion, and not fast at random data access. The
- * #GtkListStore sets the #GTK_TREE_MODEL_ITERS_PERSIST flag, which means
- * that #GtkTreeIters can be cached while the row exists. Thus, if
- * access to a particular row is needed often and your code is expected to
- * run on older versions of GTK+, it is worth keeping the iter around.
+ * Internally, the #GtkListStore was originally implemented with a linked list
+ * with a tail pointer. As a result, it was fast at data insertion and deletion,
+ * and not fast at random data access. The #GtkListStore sets the
+ * #GTK_TREE_MODEL_ITERS_PERSIST flag, which means that #GtkTreeIters can be
+ * cached while the row exists. Thus, if access to a particular row is needed
+ * often and your code is expected to run on older versions of GTK, it is worth
+ * keeping the iter around.
*
* # Atomic Operations
*