mirror of
https://github.com/sigmasternchen/php-doc-en
synced 2025-03-16 00:48:54 +00:00
new structure applied
git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@90681 c90b9560-bf6c-de11-be94-00142212c4b1
This commit is contained in:
Friedhelm Betz
parent
ce41a4d1cb
commit
59140ae2c9
3 changed files with 187 additions and 88 deletions
|
|
@ -1,24 +1,55 @@
|
|||
<?xml version="1.0" encoding="iso-8859-1"?>
|
||||
<!-- $Revision: 1.2 $ -->
|
||||
<!-- $Revision: 1.3 $ -->
|
||||
<reference id="ref.outcontrol">
|
||||
<title>Output Control Functions</title>
|
||||
<titleabbrev>Output Control</titleabbrev>
|
||||
|
||||
<partintro>
|
||||
<para>
|
||||
The Output Control functions allow you to control when output is
|
||||
sent from the script. This can be useful in several different
|
||||
situations, especially if you need to send headers to the browser
|
||||
after your script has began outputting data. The Output Control
|
||||
functions do not affect headers sent using
|
||||
<function>header</function> or <function>setcookie</function>,
|
||||
only functions such as <function>echo</function> and data between
|
||||
blocks of PHP code.
|
||||
</para>
|
||||
<para>
|
||||
<example>
|
||||
<title>Output Control example</title>
|
||||
<programlisting role="php">
|
||||
<section id="outcontrol.intro">
|
||||
&reftitle.intro;
|
||||
<para>
|
||||
The Output Control functions allow you to control when output is
|
||||
sent from the script. This can be useful in several different
|
||||
situations, especially if you need to send headers to the browser
|
||||
after your script has began outputting data. The Output Control
|
||||
functions do not affect headers sent using
|
||||
<function>header</function> or <function>setcookie</function>,
|
||||
only functions such as <function>echo</function> and data between
|
||||
blocks of PHP code.
|
||||
</para>
|
||||
</section>
|
||||
|
||||
<section id="outcontrol.requirenments">
|
||||
&reftitle.required;
|
||||
&no.requirement;
|
||||
</section>
|
||||
|
||||
<section id="outcontrol.installation">
|
||||
&reftitle.install;
|
||||
&no.install;
|
||||
</section>
|
||||
|
||||
<section id="outcontrol.configuration">
|
||||
&reftitle.runtime;
|
||||
&no.config;
|
||||
</section>
|
||||
|
||||
<section id="outcontrol.resources">
|
||||
&reftitle.resources;
|
||||
&no.resource;
|
||||
</section>
|
||||
|
||||
<section id="outcontrol.constants">
|
||||
&reftitle.constants;
|
||||
&no.constants;
|
||||
</section>
|
||||
|
||||
<section id="outcontrol.examples">
|
||||
&reftitle.examples;
|
||||
<para>
|
||||
<example>
|
||||
<title>Output Control example</title>
|
||||
<programlisting role="php">
|
||||
<![CDATA[
|
||||
<?php
|
||||
|
||||
|
|
@ -31,21 +62,26 @@ ob_end_flush();
|
|||
|
||||
?>
|
||||
]]>
|
||||
</programlisting>
|
||||
</example>
|
||||
</para>
|
||||
<para>
|
||||
In the above example, the output from <function>echo</function>
|
||||
would be stored in the output buffer until
|
||||
<function>ob_end_flush</function> was called. In the mean time,
|
||||
the call to <function>setcookie</function> successfully stored a
|
||||
cookie without causing an error. (You can not normally send
|
||||
headers to the browser after data has already been sent.)
|
||||
</para>
|
||||
<para>
|
||||
See also <function>header</function> and
|
||||
<function>setcookie</function>.
|
||||
</para>
|
||||
</programlisting>
|
||||
</example>
|
||||
</para>
|
||||
<para>
|
||||
In the above example, the output from <function>echo</function>
|
||||
would be stored in the output buffer until
|
||||
<function>ob_end_flush</function> was called. In the mean time,
|
||||
the call to <function>setcookie</function> successfully stored a
|
||||
cookie without causing an error. (You can not normally send
|
||||
headers to the browser after data has already been sent.)
|
||||
</para>
|
||||
</section>
|
||||
|
||||
<section id="outcontrol.seealso">
|
||||
&reftitle.seealso;
|
||||
<para>
|
||||
See also <function>header</function> and
|
||||
<function>setcookie</function>.
|
||||
</para>
|
||||
</section>
|
||||
</partintro>
|
||||
|
||||
&reference.outcontrol.functions;
|
||||
|
|
|
|||
|
|
@ -1,30 +1,63 @@
|
|||
<?xml version="1.0" encoding="iso-8859-1"?>
|
||||
<!-- $Revision: 1.1 $ -->
|
||||
<!-- $Revision: 1.2 $ -->
|
||||
<reference id="ref.overload">
|
||||
<title>Object property and method call overloading</title>
|
||||
<titleabbrev>Object overloading</titleabbrev>
|
||||
|
||||
<partintro id="overload.partintro">
|
||||
&warn.experimental;
|
||||
<para>
|
||||
The purpose of this extension is to allow overloading of object
|
||||
property access and method calls. Only one function is defined
|
||||
in this extension, <function>overload</function> which
|
||||
takes the name of the class that should have this functionality
|
||||
enabled. The class named has to define appropriate methods if
|
||||
it wants to have this functionality: <literal>__get()</literal>,
|
||||
<literal>__set()</literal> and <literal>__call()</literal>
|
||||
respectively for getting/setting a property, or calling a method.
|
||||
This way overloading can be selective. Inside these handler
|
||||
functions the overloading is disabled so you can access object
|
||||
properties normally.
|
||||
</para>
|
||||
<para>
|
||||
Some simple examples on using the <function>overload</function>
|
||||
function:
|
||||
<example>
|
||||
<title>Overloading a PHP class</title>
|
||||
<programlisting role="php">
|
||||
<partintro>
|
||||
|
||||
<section id="overload.intro">
|
||||
&reftitle.intro;
|
||||
<para>
|
||||
The purpose of this extension is to allow overloading of object
|
||||
property access and method calls. Only one function is defined
|
||||
in this extension, <function>overload</function> which
|
||||
takes the name of the class that should have this functionality
|
||||
enabled. The class named has to define appropriate methods if
|
||||
it wants to have this functionality: <literal>__get()</literal>,
|
||||
<literal>__set()</literal> and <literal>__call()</literal>
|
||||
respectively for getting/setting a property, or calling a method.
|
||||
This way overloading can be selective. Inside these handler
|
||||
functions the overloading is disabled so you can access object
|
||||
properties normally.
|
||||
</para>
|
||||
&warn.experimental;
|
||||
</section>
|
||||
|
||||
<section id="overload.requirenments">
|
||||
&reftitle.required;
|
||||
&no.requirement;
|
||||
</section>
|
||||
|
||||
<section id="overload.installation">
|
||||
&reftitle.install;
|
||||
<para>
|
||||
</para>
|
||||
</section>
|
||||
|
||||
<section id="overload.configuration">
|
||||
&reftitle.runtime;
|
||||
&no.config;
|
||||
</section>
|
||||
|
||||
<section id="overload.resources">
|
||||
&reftitle.resources;
|
||||
&no.resource;
|
||||
</section>
|
||||
|
||||
<section id="overload.constants">
|
||||
&reftitle.constants;
|
||||
&no.constants;
|
||||
</section>
|
||||
|
||||
<section id="overload.examples">
|
||||
&reftitle.examples;
|
||||
<para>
|
||||
Some simple examples on using the <function>overload</function>
|
||||
function:
|
||||
<example>
|
||||
<title>Overloading a PHP class</title>
|
||||
<programlisting role="php">
|
||||
<![CDATA[
|
||||
<?php
|
||||
|
||||
|
|
@ -76,20 +109,21 @@ var_dump($o->a[0]->prop);
|
|||
|
||||
?>
|
||||
]]>
|
||||
</programlisting>
|
||||
</example>
|
||||
</para>
|
||||
<warning>
|
||||
<para>
|
||||
As this is an experimental extension, not all things
|
||||
work. There is no <literal>__call()</literal> support
|
||||
currently, you can only overload the get and set
|
||||
operations for properties. You cannot invoke the
|
||||
original overloading handlers of the class, and
|
||||
<literal>__set()</literal> only works to one level
|
||||
of property access.
|
||||
</programlisting>
|
||||
</example>
|
||||
</para>
|
||||
</warning>
|
||||
<warning>
|
||||
<para>
|
||||
As this is an experimental extension, not all things
|
||||
work. There is no <literal>__call()</literal> support
|
||||
currently, you can only overload the get and set
|
||||
operations for properties. You cannot invoke the
|
||||
original overloading handlers of the class, and
|
||||
<literal>__set()</literal> only works to one level
|
||||
of property access.
|
||||
</para>
|
||||
</warning>
|
||||
</section>
|
||||
</partintro>
|
||||
|
||||
&reference.overload.functions;
|
||||
|
|
|
|||
|
|
@ -1,28 +1,55 @@
|
|||
<?xml version="1.0" encoding="iso-8859-1"?>
|
||||
<!-- $Revision: 1.3 $ -->
|
||||
<!-- $Revision: 1.4 $ -->
|
||||
<reference id="ref.ovrimos">
|
||||
<title>Ovrimos SQL functions</title>
|
||||
<titleabbrev>OvrimosSQL</titleabbrev>
|
||||
|
||||
<partintro>
|
||||
<para>
|
||||
Ovrimos SQL Server, is a client/server, transactional RDBMS
|
||||
combined with Web capabilities and fast transactions.
|
||||
</para>
|
||||
<para>
|
||||
Ovrimos SQL Server is available at <ulink
|
||||
url="&url.ovrimos;">www.ovrimos.com</ulink>. To enable ovrimos
|
||||
support in PHP just compile PHP with the <option
|
||||
role="configure">--with-ovrimos</option>
|
||||
parameter to configure script. You'll need to install the sqlcli
|
||||
library available in the Ovrimos SQL Server distribution.
|
||||
</para>
|
||||
<para>
|
||||
<example>
|
||||
<title>
|
||||
Connect to Ovrimos SQL Server and select from a system table
|
||||
</title>
|
||||
<programlisting role="php">
|
||||
<section id="ovrimos.intro">
|
||||
&reftitle.intro;
|
||||
<para>
|
||||
Ovrimos SQL Server, is a client/server, transactional RDBMS
|
||||
combined with Web capabilities and fast transactions.
|
||||
</para>
|
||||
</section>
|
||||
|
||||
<section id="ovrimos.requirenments">
|
||||
&reftitle.required;
|
||||
<para>
|
||||
Ovrimos SQL Server is available at <ulink
|
||||
url="&url.ovrimos;">&url.ovrimos;</ulink>. You'll need to install the
|
||||
sqlcli library available in the Ovrimos SQL Server distribution.
|
||||
</para>
|
||||
</section>
|
||||
|
||||
<section id="ovrimos.installation">
|
||||
&reftitle.install;
|
||||
<para>
|
||||
To enable Ovrimos support in PHP just compile PHP with the
|
||||
<option role="configure">--with-ovrimos</option>
|
||||
parameter to configure script.
|
||||
</para>
|
||||
</section>
|
||||
|
||||
<section id="ovrimos.configuration">
|
||||
&reftitle.runtime;
|
||||
&no.config;
|
||||
</section>
|
||||
|
||||
<section id="ovrimos.resources">
|
||||
&reftitle.resources;
|
||||
<para>
|
||||
</para>
|
||||
</section>
|
||||
|
||||
<section id="ovrimos.examples">
|
||||
&reftitle.examples;
|
||||
<para>
|
||||
<example>
|
||||
<title>
|
||||
Connect to Ovrimos SQL Server and select from a system table
|
||||
</title>
|
||||
<programlisting role="php">
|
||||
<![CDATA[
|
||||
<?php
|
||||
$conn = ovrimos_connect ("server.domain.com", "8001", "admin", "password");
|
||||
|
|
@ -38,10 +65,12 @@ if ($conn != 0) {
|
|||
}
|
||||
?>
|
||||
]]>
|
||||
</programlisting>
|
||||
</example>
|
||||
This will just connect to an Ovrimos SQL server.
|
||||
</para>
|
||||
</programlisting>
|
||||
</example>
|
||||
This will just connect to an Ovrimos SQL server.
|
||||
</para>
|
||||
</section>
|
||||
|
||||
</partintro>
|
||||
|
||||
&reference.ovrimos.functions;
|
||||
|
|
|
|||
Loading…
Reference in a new issue