Changes between Version 2 and Version 3 of GRefPtr

Timestamp:

Jan 20, 2014 3:18:26 AM (10 years ago)

Author:

Adrian Perez de Castro

Comment:

--

GRefPtr

@@ -18 +18 @@
 {{{
 #!cpp
-GRefPtr<GtkWidget> widget;
+GRefPtr<GMainContext> context;
 // Check always succeeds, nullptr is the default value.
-ASSERT(!widget);
+ASSERT(!context);
 }}}
 
-It is also possible to pass an initial value to the constructor — it can be both a raw pointer or a `GRefPtr` of the same type:
-{{{
-#!cpp
-void doWithWidget(GtkWidget* widget) {
-    GRefPtr<GtkWidget> widgetLocal1(widget); // Increases the reference counter of “widget”
-    GRefPtr<GtkWidget> widgetLocal2(widgetLocal1); // ...and again.
-}
-}}}
+=== Destruction ===
 
 When a `GRefPtr<T>` goes is destroyed, it decreases the reference count of the object it holds.
 
-=== Adopting a pointer ===
 
-Sometimes it is desirable to store a pointer in a `GRefPtr` without increasing the reference counter. The main use case is assigning a newly created instance to a `GRefPtr`: the newly created instance already has a reference count of ''one'' and assigning it to a `GRefPtr` would increase the reference count to ''two'', which would be incorrect. To avoid this, the `adoptGRef()` helper function is provided. This function creates a `GRefPtr` without increasing the reference counter of the object it holds. This is incorrect:
+=== Adopting a reference ===
+
+Sometimes it is desirable to store a pointer in a `GRefPtr` without increasing the reference counter. The main use case is assigning a newly created instance to a `GRefPtr`: the newly created instance already has a reference count of ''one'' and assigning it to a `GRefPtr` would increase the reference count to ''two'', which would be incorrect (and very likely would cause a leak). To avoid this, the `adoptGRef()` helper function is provided. This function creates a `GRefPtr` without increasing the reference counter of the object it holds. This is incorrect:
 {{{
 #!cpp