File: method.xml

package info (click to toggle)
php-doc 20100521-2
  • links: PTS, VCS
  • area: main
  • in suites: squeeze, wheezy
  • size: 59,992 kB
  • ctags: 4,085
  • sloc: xml: 796,833; php: 21,338; cpp: 500; sh: 117; makefile: 58; awk: 28
file content (223 lines) | stat: -rw-r--r-- 6,175 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
<?xml version="1.0" encoding="utf-8"?>
<!-- $Revision: 299459 $ -->

<refentry xml:id="classname.methodname" xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink">
 <refnamediv>
  <!-- If this is a method, use this -->
  <refname>ClassName::methodName</refname>
  <!-- If this is a property, use this instead -->
  <refname>ClassName->propertyName</refname>
<!-- IF OOP & PROCEDURAL

IN GENERAL:  If this method also has a procedural mapping, please use the
instructions and code found inside the "IF OOP & PROCEDURAL" comments.

REFNAME:  Procedural refname goes after the OOP refname.

  <refname>function_name</refname>
-->
  <refpurpose>The methodName purpose</refpurpose>
 </refnamediv>

 <refsect1 role="description">
  &reftitle.description;
<!-- IF OOP & PROCEDURAL.
  <para>&style.oop;</para>
-->
<!-- Use constructorsynopsis and destructorsynopsis rather than methodsynopsis for __construct and __destruct
     There is no return <type> for the constructorsynopsis/destructorsynopsis -->
  <methodsynopsis role="oop">
   <!-- Example: All methods have this. Don't use <void> for the return type, use <type>void</type> instead. -->
   <type>thereturned type</type><methodname>ClassName::methodName</methodname>
   <!-- Example: Required parameter -->
   <methodparam><type>param1type</type><parameter>firstparameter</parameter></methodparam>
   <!-- Example: Optional parameter, also by reference -->
   <methodparam choice="opt"><type>int</type><parameter role="reference">secondparameter</parameter><initializer>defaultvalue</initializer></methodparam>
   <!-- Example: If no methodparams exist (void), use this -->
   <void />
  </methodsynopsis>
<!-- If this is a property, not a method, use this instead
  <classsynopsis>
   <ooclass><classname>className</classname></ooclass>
   <fieldsynopsis><modifier>public</modifier><modifier>static</modifier><type>string</type><varname>name</varname></fieldsynopsis>
  </classsynopsis>
-->
<!-- IF OOP & PROCEDURAL

Procedural synopsis goes after OOP synopsis.

  <para>&style.procedural;</para>
  <methodsynopsis role="procedural">
   [Fill in function's parameter details just like in
   function.xml/refentry/refsect1[@role=description]/methodsynopsis]
  </methodsynopsis>
-->
  <para>
   The function description goes here.
  </para>
 </refsect1>

 <refsect1 role="parameters">
  &reftitle.parameters;
  <variablelist>
   <varlistentry>
    <term><parameter>firstparameter</parameter></term>
    <listitem>
     <para>
      Its description
     </para>
    </listitem>
   </varlistentry>
   <varlistentry>
    <term><parameter>secondparameter</parameter></term>
    <listitem>
     <para>
      Its description
     </para>
    </listitem>
   </varlistentry>
  </variablelist>
 </refsect1>

 <refsect1 role="returnvalues">
  &reftitle.returnvalues;
  <para>
   What this function returns, first on success, then failure.  If simply
   true on success and false on failure, just use &return.success; here.
  </para>
 </refsect1>

 <refsect1 role="errors">
  &reftitle.errors;
  <para>
   When does this function issue E_* level errors, and/or throw exceptions.
  </para>
 </refsect1>

 <refsect1 role="unicode">
  &reftitle.unicode;
  <para>
   Information specific to unicode, from the PHP 6 changes.
  </para>
 </refsect1>

 <refsect1 role="changelog">
  &reftitle.changelog;
  <informaltable>
   <tgroup cols="2">
    <thead>
     <row>
      <entry>&Version;</entry>
      <entry>&Description;</entry>
     </row>
    </thead>
    <tbody>
     <row>
      <entry>Enter the version of change here</entry>
      <entry>
       Describe the change
      </entry>
     </row>
    </tbody>
   </tgroup>
  </informaltable>
 </refsect1>

 <refsect1 role="examples">
  &reftitle.examples;
  <example xml:id="classname.methodname.example.basic">
   <title><methodname>ClassName::methodName</methodname> example</title>
   <para>
     Any text that describes the purpose of the example, or what
     goes on in the example should be here. (Inside the <example> tag, not out).
   </para>
<!-- IF OOP & PROCEDURAL
   <para>&style.oop;</para>
-->
   <programlisting role="php">
<![CDATA[
<?php
if ($anexample === true) {
    echo 'Use the PEAR Coding standards';
}
if ($thereisoutput === 'and it is multiple lines') {
    echo 'Use a screen like we did below';
}
?>
]]>
   </programlisting>
<!-- IF OOP & PROCEDURAL

The first example should be a very basic demonstration of how to do the
same task in both OOP and procedural PHP. Each of these demonstrations
should be in their own program listings with the appropriate &style.*
entity above it. The OOP way must be first.

   <para>&style.procedural;</para>
   <programlisting role="php">
<![CDATA[
<?php
echo same_task_as_above();
?>
]]>
   </programlisting>

Also, use these plural output entities instead:
   &examples.outputs;
   &examples.outputs.similar;
-->
   &example.outputs;
   <screen>
<![CDATA[
Use the PEAR Coding standards
Use a screen like we did below
]]>
   </screen>
  </example>
 </refsect1>

 <refsect1 role="notes">
  &reftitle.notes;
  <caution>
   <para>
    Any notes that don't fit anywhere else should go here.
    90% of the time, notes, warnings or cautions are better placed in the
    parameters section. Consider that before using this section!
   </para>
  </caution>
  &note.language-construct;
  &note.not-bin-safe;
  &note.registerglobals;
 </refsect1>

 <refsect1 role="seealso">
  &reftitle.seealso;
  <simplelist>
   <member><methodname>ClassName::otherMethodName</methodname></member>
   <member><function>somefunc</function></member>
   <member>The <link linkend="something">something appendix</link></member>
  </simplelist>
 </refsect1>

</refentry>

<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:1
sgml-indent-data:t
indent-tabs-mode:nil
sgml-parent-document:nil
sgml-default-dtd-file:"~/.phpdoc/manual.ced"
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
End:
vim600: syn=xml fen fdm=syntax fdl=2 si
vim: et tw=78 syn=sgml
vi: ts=1 sw=1
-->