git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@271124 c90b9560-bf6c-de11-be94-00142212c4b1
This commit is contained in:
Philip Olson 2008-12-13 08:08:30 +00:00
parent fb32b71aef
commit b7884d7feb
4 changed files with 14 additions and 14 deletions

View file

@ -1,5 +1,5 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!-- $Revision: 1.37 $ -->
<!-- $Revision: 1.38 $ -->
<appendix xml:id="migration52" xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink">
<title>Migrating from PHP 5.1.x to PHP 5.2.x</title>
<para>
@ -940,7 +940,7 @@ $obj->getCommentName('');
</listitem>
<listitem>
<simpara>
void swfmovie::protect([string pasword])
void swfmovie::protect([string password])
- Protects
</simpara>
</listitem>

View file

@ -1,5 +1,5 @@
<?xml version="1.0" encoding="ISO-8859-1" ?>
<!-- $Revision: 1.4 $ -->
<!-- $Revision: 1.5 $ -->
<part xml:id="internals2.counter" xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xi="http://www.w3.org/2001/XInclude">
<title>The "counter" Extension - A Continuing Example</title>
@ -105,7 +105,7 @@
Tells "counter" where to save data that has to persist between
invocations of PHP (i.e. any counter that has COUNTER_RESET_NEVER or
COUNTER_FLAG_SAVE). A file will be created at this path, which must be
readable and writeable to whatever user PHP is running as.
readable and writable to whatever user PHP is running as.
</simpara>
</listitem>
</varlistentry>

View file

@ -1,5 +1,5 @@
<?xml version="1.0" encoding="ISO-8859-1" ?>
<!-- $Revision: 1.1 $ -->
<!-- $Revision: 1.2 $ -->
<sect1 xml:id="internals2.structure.basics" xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink">
<title>Basic constructs</title>
@ -18,16 +18,16 @@
understandable, but C forces certain necessary declarations upon any
extension that to an inexperienced eye seem redundant or plain unnecessary.
All of those constructs, detailed in this section, are "write once and
forget" in Zend Engine 2 and 3. Here are some excerpts from the pregenerated
forget" in Zend Engine 2 and 3. Here are some excerpts from the pre-generated
<filename>php_counter.h</filename> and <filename>counter.c</filename> files
created by PHP 5.3's <command>ext_skel</command>, showing the pregenerated
created by PHP 5.3's <command>ext_skel</command>, showing the pre-generated
declarations:
</simpara>
<note>
<simpara>
The astute reader will notice that there are several delcarations in the
real files that aren't shown here. Those declaractions are specific to
The astute reader will notice that there are several declarations in the
real files that aren't shown here. Those declarations are specific to
various Zend subsystems and are discussed elsewhere as appropriate.
</simpara>
</note>

View file

@ -1,5 +1,5 @@
<?xml version="1.0" encoding="ISO-8859-1" ?>
<!-- $Revision: 1.5 $ -->
<!-- $Revision: 1.6 $ -->
<sect1 xml:id="internals2.structure.globals" xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink">
<title>Extension globals</title>
@ -16,7 +16,7 @@
<listitem>
<simpara>
Barring any special options passed to the compiler, a global varaible can
Barring any special options passed to the compiler, a global variable can
be accessed and changed by any piece of code anywhere in the program,
whether or not that code should be doing so.
</simpara>
@ -40,7 +40,7 @@
A PHP extension's globals are more properly called the "extension state",
since most modules must remember what they're doing between function calls.
The "counter" extension is a perfect example of this need: The basic
interface calls for a counter with a persistant value. A programmer new to
interface calls for a counter with a persistent value. A programmer new to
Zend and PHP might do something like this in <filename>counter.c</filename>
to store that value:
</simpara>
@ -67,12 +67,12 @@ PHP_FUNCTION(counter_get)
it would function correctly. However, there are a number of situations in
which more than one copy of PHP is running in the same thread, which means
more than one instance of the counter module. Suddenly these multiple
threads are sharing the same counter value, which is clearly undesireable.
threads are sharing the same counter value, which is clearly undesirable.
Another problem shows itself when considering that another extension might
someday happen to have a global with the same name, and due to the rules of
C scoping, this has the potential to cause a compile failure, or worse, a
runtime error. Something more elaborate is needed, and so exists Zend's
support for threadsafe per-module globals.
support for thread-safe per-module globals.
</simpara>
</sect2>