summaryrefslogtreecommitdiff
path: root/pages
diff options
context:
space:
mode:
authorXavi Artigas <xavierartigas@yahoo.es>2017-11-09 04:09:26 -0800
committerapache <apache@e5-web1.enlightenment.org>2017-11-09 04:09:26 -0800
commit80fd17f16bd0684e1327d841c524d1e70993f1d6 (patch)
tree2413e23b05424de1b50959e23d126224443c477c /pages
parent364351986343b599a33615cce3584d1ba8642aaf (diff)
Wiki page eo-intro.md changed with summary [] by Xavi Artigas
Diffstat (limited to 'pages')
-rw-r--r--pages/develop/tutorial/c/eo-intro.md.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/pages/develop/tutorial/c/eo-intro.md.txt b/pages/develop/tutorial/c/eo-intro.md.txt
index c3e0b7fa3..aff7847d9 100644
--- a/pages/develop/tutorial/c/eo-intro.md.txt
+++ b/pages/develop/tutorial/c/eo-intro.md.txt
@@ -96,7 +96,7 @@ At this point, you have created your first Eo object. It is time now to talk abo
96 96
97### Reference Counting ### 97### Reference Counting ###
98 98
99In the simplest case, when only one piece of code is interacting with an object, you can create the object, use it, and then destroy it. In more complex scenarios though, when different parts of the code use the same object, maybe from different execution threads, it is not easy to know when an object is not in use anymore and can therefore be safely destroyed. 99In the simplest case, when only one piece of code is interacting with an object, you can create the object, use it, and then destroy it. In more complex scenarios though, when different parts of the code use the same object, it is not easy to know when an object is not in use anymore and can therefore be safely destroyed.
100 100
101A common approach to this problem is to use the **Reference Counting** technique, in which every object keeps track of how many people (pieces of code) are using it in an internal *reference counter*: 101A common approach to this problem is to use the **Reference Counting** technique, in which every object keeps track of how many people (pieces of code) are using it in an internal *reference counter*:
102 102