summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPhilip Withnall <philip@tecnocode.co.uk>2022-10-26 08:32:40 +0000
committerPhilip Withnall <philip@tecnocode.co.uk>2022-10-26 08:32:40 +0000
commited05da29f723b5951e2e183ec0dbe3f5d1ed6ab4 (patch)
tree3d5e4bf283bc2f4e052832cf36e44a2afa3d3937
parente562c3b8a346efbae7117b5660bdaecb40760615 (diff)
parentea1b2cba0c9308dc84c5c5d37b6778faf726d27f (diff)
downloadglib-ed05da29f723b5951e2e183ec0dbe3f5d1ed6ab4.tar.gz
Merge branch 'cesun/fix-add-instance-private-typo' into 'main'
Fix function name typo in comment of gtype.c Closes #2791 See merge request GNOME/glib!3016
-rw-r--r--gobject/gtype.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/gobject/gtype.c b/gobject/gtype.c
index 66db7bc9d..7a10f444e 100644
--- a/gobject/gtype.c
+++ b/gobject/gtype.c
@@ -4774,7 +4774,7 @@ g_type_add_instance_private (GType class_gtype,
* hide it behind a macro. the function will return the private size, instead
* of the offset, which will be stored inside a static variable defined by
* the G_DEFINE_TYPE_EXTENDED() macro. the G_DEFINE_TYPE_EXTENDED() macro will
- * check the variable and call g_type_class_add_instance_private(), which
+ * check the variable and call g_type_class_adjust_private_offset(), which
* will use the data size and actually register the private data, then
* return the computed offset of the private data, which will be stored
* inside the static variable, so we can use it to retrieve the pointer
@@ -4783,7 +4783,7 @@ g_type_add_instance_private (GType class_gtype,
* once all our code has been migrated to the new idiomatic form of private
* data registration, we will change the g_type_add_instance_private()
* function to actually perform the registration and return the offset
- * of the private data; g_type_class_add_instance_private() already checks
+ * of the private data; g_type_class_adjust_private_offset() already checks
* if the passed argument is negative (meaning that it's an offset in the
* GTypeInstance allocation) and becomes a no-op if that's the case. this
* should make the migration fully transparent even if we're effectively