com gtk/php-gtk: 'Naming conventions' should be where the intro says.: CODING_STANDARDS

Commit:    077b9f3640d0240279f891e27a977a164d7b9baa
Author:    Steph Fox <[email protected]>         Wed, 26 Oct 2005 13:22:16 +0000
Parents:   b6808891303c16be7c678602ff3ae7a0c184dc7a
Branches:  master

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

Log:
'Naming conventions' should be where the intro says.

Changed paths:
  M  CODING_STANDARDS


Diff:
077b9f3640d0240279f891e27a977a164d7b9baa
diff --git a/CODING_STANDARDS b/CODING_STANDARDS
index b431ebc..bdb7ee7 100644
--- a/CODING_STANDARDS
+++ b/CODING_STANDARDS
@@ -15,6 +15,10 @@ is available online at http://pear.php.net/manual/en/standards.php.
 
 Overview:
 
+File formats:
+  ISO-8859-1, text/ASCII, Unix line endings, single line feed after
+  content.
+
 Indenting and line length:
   No tabs, indent 4 spaces, aim to hard wrap at 78 characters (the PEAR
   CS suggests 75 to 85 is 'safe', but in documentation it may not be).
@@ -95,6 +99,3 @@ 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 uppercased identifier, e.g. $_MYCLASS_global_varname.
-
-File formats:
-  ISO-8859-1, text/ASCII, Unix line endings, single line feed after content.