From c4ca59647de6c8716a76645b6689b58425e8a116 Mon Sep 17 00:00:00 2001
From: legenerationlazi <legenerationlazi@625475ce-881a-0410-a577-b389adb331d8>
Date: Fri, 13 Apr 2007 19:32:57 +0000
Subject: [PATCH] testing conversion to wiki markup script

---
 ...- Coding Style - Functions and methods.php | 95 ++++++++-----------
 1 file changed, 42 insertions(+), 53 deletions(-)

diff --git a/manual/docs/Coding standards - Coding Style - Functions and methods.php b/manual/docs/Coding standards - Coding Style - Functions and methods.php
index a7f8b0d94..8b15661c0 100644
--- a/manual/docs/Coding standards - Coding Style - Functions and methods.php	
+++ b/manual/docs/Coding standards - Coding Style - Functions and methods.php	
@@ -1,22 +1,21 @@
 <?php ?>
-<ul>
-<li \>Methods must be named by following the naming conventions.
-</ul>
-<ul>
-<li \>Methods must always declare their visibility by using one of the private, protected, or public constructs.
-</ul>
-<ul>
-<li \>Like classes, the brace is always written right after the method name. There is no space between the function name and the opening parenthesis for the arguments.
-</ul>
-<ul>
-<li \>Functions in the global scope are strongly discouraged.
-</ul>
-<ul>
-<li \>This is an example of an acceptable function declaration in a class:
-</ul>
 
-<?php
-renderCode("<?php
+* Methods must be named by following the naming conventions.
+
+
+* Methods must always declare their visibility by using one of the private, protected, or public constructs.
+
+
+* Like classes, the brace is always written right after the method name. There is no space between the function name and the opening parenthesis for the arguments.
+
+
+* Functions in the global scope are strongly discouraged.
+
+
+* This is an example of an acceptable function declaration in a class:
+
+
+<code type="php">
 /**
  * Documentation Block Here
  */
@@ -28,14 +27,11 @@ class Foo {
         // entire content of function
         // must be indented four spaces
     }
-}");
+}</code>
 
-?>
-<ul>
-<li \>Passing by-reference is permitted in the function declaration only:
-</ul>
-<?php
-renderCode("<?php
+* Passing by-reference is permitted in the function declaration only:
+
+<code type="php">
 /** 
  * Documentation Block Here 
  */
@@ -46,16 +42,14 @@ class Foo {
     public function bar(&\$baz) {
     }
 }
-");
-?>
-<ul>
-<li \>Call-time pass by-reference is prohibited.
-</ul>
-<ul>
-<li \>The return value must not be enclosed in parentheses. This can hinder readability and can also break code if a method is later changed to return by reference.
-</ul>
-<?php
-renderCode("<?php
+</code>
+
+* Call-time pass by-reference is prohibited.
+
+
+* The return value must not be enclosed in parentheses. This can hinder readability and can also break code if a method is later changed to return by reference.
+
+<code type="php">
 /** 
  * Documentation Block Here 
  */
@@ -72,29 +66,24 @@ class Foo {
     public function bar() {        
         return \$this->bar;
     }
-}");
-?>
-<ul>
-<li \>Function arguments are separated by a single trailing space after the comma delimiter. This is an example of an acceptable function call for a function that takes three arguments:
-</ul>
-<?php
-renderCode("<?php
+}</code>
+
+* Function arguments are separated by a single trailing space after the comma delimiter. This is an example of an acceptable function call for a function that takes three arguments:
+
+<code type="php">
 threeArguments(1, 2, 3);
-?>");
-?>
-<ul>
-<li \>Call-time pass by-reference is prohibited. See the function declarations section for the proper way to pass function arguments by-reference.
-</ul>
-<ul>
-<li \>For functions whose arguments permitted arrays, the function call may include the "array" construct and can be split into multiple lines to improve readability. In these cases, the standards for writing arrays still apply:
-</ul>
-<?php
-renderCode("<?php
+?></code>
+
+* Call-time pass by-reference is prohibited. See the function declarations section for the proper way to pass function arguments by-reference.
+
+
+* For functions whose arguments permitted arrays, the function call may include the "array" construct and can be split into multiple lines to improve readability. In these cases, the standards for writing arrays still apply:
+
+<code type="php">
 threeArguments(array(1, 2, 3), 2, 3);
 
 threeArguments(array(1, 2, 3, 'Framework',
                      'Doctrine', 56.44, 500), 2, 3);
-?>");
-?>
+?></code>