[gnome-devel-docs/wip/swilmet/various-fixes: 2/2] programming-guidelines: use class instead of object where appropriate



commit 044047d582196ef4f387a07c3080500080f490b0
Author: Sébastien Wilmet <swilmet gnome org>
Date:   Thu Apr 16 14:50:45 2015 +0200

    programming-guidelines: use class instead of object where appropriate
    
    For a method: a method is part of a class, not for a specific object.
    
    For headers: a header generally contains a class definition, not an
    object.

 programming-guidelines/C/namespacing.page |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)
---
diff --git a/programming-guidelines/C/namespacing.page b/programming-guidelines/C/namespacing.page
index 1b45c7b..bf9398c 100644
--- a/programming-guidelines/C/namespacing.page
+++ b/programming-guidelines/C/namespacing.page
@@ -84,7 +84,7 @@
         still be unique.
       </p></item>
       <item><p>
-        All methods of an object should also be prefixed with the object name.
+        All methods of a class should also be prefixed with the class name.
       </p></item>
     </list>
 
@@ -97,7 +97,7 @@
 
     <p>
       For example, for a project called ‘Walbottle’, the short namespace ‘Wbl’
-      would be chosen. If it has a ‘schema’ object and a ‘writer’ object, it
+      would be chosen. If it has a ‘schema’ class and a ‘writer’ class, it
       would install headers:
     </p>
     <list>
@@ -115,7 +115,7 @@
     </p>
 
     <p>
-      For the schema object, the following symbols would be exported (amongst
+      For the schema class, the following symbols would be exported (amongst
       others), following GObject conventions:
     </p>
     <list>


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]