WWW-www.enlightenment.org pushed a commit to branch master. http://git.enlightenment.org/website/www-content.git/commit/?id=80fd17f16bd0684e1327d841c524d1e70993f1d6
commit 80fd17f16bd0684e1327d841c524d1e70993f1d6 Author: Xavi Artigas <[email protected]> Date: Thu Nov 9 04:09:26 2017 -0800 Wiki page eo-intro.md changed with summary [] by Xavi Artigas --- pages/develop/tutorial/c/eo-intro.md.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/develop/tutorial/c/eo-intro.md.txt b/pages/develop/tutorial/c/eo-intro.md.txt index c3e0b7fa..aff7847d 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 ### Reference Counting ### -In 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. +In 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. A 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*: --
