com gtk/php-gtk: Write 'PHP-GTK 2' in stone.: CODING_STANDARD S

[email protected] (David Soria Parra) Thu, 27 Oct 2005 12:46:05 +0000

Newsgroups	php.gtk.cvs
Message-ID	<[email protected]>

Commit:    2126cf13dac97966ee5164aeb3a2836b16b04928
Author:    Steph Fox <[email protected]>         Thu, 27 Oct 2005 12:46:05 +0000
Parents:   f5c44b80d1bfcd68f86d53c58f8ea5252af141a2
Branches:  master

Link:       http://git.php.net/?p=gtk/php-gtk.git;a=commitdiff;h=2126cf13dac97966ee5164aeb3a2836b16b04928

Log:
Write 'PHP-GTK 2' in stone.

Changed paths:
  M  CODING_STANDARDS


Diff:
2126cf13dac97966ee5164aeb3a2836b16b04928
diff --git a/CODING_STANDARDS b/CODING_STANDARDS
index 6ec9680..074f6b2 100644
--- a/CODING_STANDARDS
+++ b/CODING_STANDARDS
@@ -101,3 +101,8 @@ Naming conventions:
   Global variables: We can't emulate PEAR completely here, but we can stay
     with the idea of prefixing global variable names with an underscore and
     an uppercase identifier, e.g. $_MYCLASS_global_varname.
+  PHP-GTK itself should always be referred to as 'PHP-GTK', as both the PHP
+    part and the GTK part are acronyms. If you need to write about a specific
+    version in code commentary, the version number should be separated by a
+    single space, i.e. 'PHP-GTK 2', 'PHP 5', 'GTK 2'. In file or class names,
+    simply omit the space.