some new material on tests and mem mgmt, para->simpara

git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@271883 c90b9560-bf6c-de11-be94-00142212c4b1
This commit is contained in:
Gwynne Raskind 2008-12-25 21:04:11 +00:00
parent 2466f3fea0
commit 6f3202b929
6 changed files with 57 additions and 8 deletions

View file

@ -0,0 +1,9 @@
<?xml version="1.0" encoding="ISO-8859-1" ?>
<!-- $Revision: 1.1 $ -->
<sect1 xml:id="internals2.memory.TSRM" xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink">
<title>Thread-Safe Resource Manager</title>
<simpara>
</simpara>
</sect1>

View file

@ -1,9 +1,18 @@
<?xml version="1.0" encoding="ISO-8859-1" ?>
<!-- $Revision: 1.2 $ -->
<!-- $Revision: 1.3 $ -->
<chapter xml:id="internals2.memory" xmlns="http://docbook.org/ns/docbook">
<title>Memory management</title>
<para>
</para>
<simpara>
Memory management in the Zend Engine is deceptively simple. There are some
APIs to learn, and some concepts behind them to understand, but that's about
all.
</simpara>
&internals2.memory.management;
&internals2.memory.persistence;
&internals2.memory.TSRM;
</chapter>
<!-- Keep this comment at the end of the file

View file

@ -0,0 +1,9 @@
<?xml version="1.0" encoding="ISO-8859-1" ?>
<!-- $Revision: 1.1 $ -->
<sect1 xml:id="internals2.memory.management" xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink">
<title>Basic memory management</title>
<simpara>
</simpara>
</sect1>

View file

@ -0,0 +1,9 @@
<?xml version="1.0" encoding="ISO-8859-1" ?>
<!-- $Revision: 1.1 $ -->
<sect1 xml:id="internals2.memory.persistence" xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink">
<title>Data persistence</title>
<simpara>
</simpara>
</sect1>

View file

@ -1,9 +1,9 @@
<?xml version="1.0" encoding="ISO-8859-1" ?>
<!-- $Revision: 1.4 $ -->
<!-- $Revision: 1.5 $ -->
<chapter xml:id="internals2.structure" xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink">
<title>Extension structure</title>
<para>
<simpara>
Many extension-writing guides focus on simple examples first and ignore the
requirements of more complex implementations until later. Often such guides
must repeat themselves over and over in order to describe these new
@ -11,7 +11,7 @@
a mature, practical implementation, in order to prepare users for needs and
issues they will almost always encounter in the process of extension
development.
</para>
</simpara>
&internals2.structure.files;
&internals2.structure.basics;

View file

@ -1,8 +1,21 @@
<?xml version="1.0" encoding="ISO-8859-1" ?>
<!-- $Revision: 1.1 $ -->
<!-- $Revision: 1.2 $ -->
<sect1 xml:id="internals2.structure.tests" xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink">
<title>Testing an extension</title>
<para/>
<simpara>
One of the accepted requirements of good programming is testing. PHP provides
a test harness for unit regression tests, in the form of a script called
<command>run-tests.php</command>.
</simpara>
<simpara>
Tests for a particular module are stored in the <filename>tests/</filename>
subdirectory of the module's folder, and have a <filename>.phpt</filename>
extension. For details of the PHPT format, see
<link xlink:href="http://qa.php.net/write-test.php"/>.
</simpara>
</sect1>
<!-- Keep this comment at the end of the file