2004-04-20 11:27:15 +00:00
|
|
|
<!-- $Revision$ -->
|
|
|
|
|
|
|
|
<!ENTITY note.parameter.merge '<note>
|
|
|
|
<title>Technical Note</title>
|
|
|
|
<para>
|
|
|
|
The <parameter>merge</parameter> parameter respects array keys, so if
|
|
|
|
you merge two numerically indexed arrays, they may overwrite each other
|
2006-09-26 22:41:21 +00:00
|
|
|
or result in non-sequential keys. This is unlike the PHP
|
|
|
|
<ulink url="&url.php-manual;array_merge">
|
|
|
|
<varname>array_merge()</varname></ulink> function
|
|
|
|
which wipes out numerical keys and renumbers them.
|
2004-04-20 11:27:15 +00:00
|
|
|
</para>
|
|
|
|
</note>'>
|
2004-04-20 11:37:05 +00:00
|
|
|
|
2007-06-18 20:45:33 +00:00
|
|
|
<!ENTITY note.parameter.function '<note>
|
|
|
|
<title>Technical Note</title>
|
|
|
|
<para>
|
|
|
|
If the chosen <parameter>function</parameter> callback is of the form
|
|
|
|
<literal>array(&$object, $method)</literal>, only one instance of the
|
|
|
|
same class and with the same <literal>$method</literal> can be registered. The
|
|
|
|
latest registered <parameter>function</parameter> callback will be used in
|
|
|
|
such a scenario.
|
|
|
|
</para>
|
|
|
|
</note>'>
|
|
|
|
|
2004-04-20 11:37:05 +00:00
|
|
|
<!ENTITY parameter.compileid '<para>
|
2005-05-27 16:25:02 +00:00
|
|
|
As an optional third parameter, you can pass a
|
2005-06-10 07:16:47 +00:00
|
|
|
<parameter>$compile_id</parameter>.
|
2004-04-20 11:37:05 +00:00
|
|
|
This is in the event that you want to compile different versions of
|
|
|
|
the same template, such as having separate templates compiled
|
2005-05-27 16:25:02 +00:00
|
|
|
for different languages. Another use for
|
2005-06-10 07:16:47 +00:00
|
|
|
<parameter>$compile_id</parameter> is when you use more than one
|
2006-09-26 22:41:21 +00:00
|
|
|
<link linkend="variable.template.dir"><parameter>$template_dir</parameter></link>
|
|
|
|
but only one
|
|
|
|
<link linkend="variable.compile.dir"><parameter>$compile_dir</parameter></link>.
|
2005-05-23 15:43:01 +00:00
|
|
|
Set a separate <parameter>$compile_id</parameter> for each
|
2006-09-26 22:41:21 +00:00
|
|
|
<link linkend="variable.template.dir"><parameter>$template_dir</parameter></link>,
|
|
|
|
otherwise templates of the same name will overwrite each other. You can
|
|
|
|
also set the <link linkend="variable.compile.id">
|
|
|
|
<parameter>$compile_id</parameter></link> variable once instead of passing
|
|
|
|
this to each call to this function.
|
2004-04-20 11:37:05 +00:00
|
|
|
</para>'>
|
2006-09-26 22:41:21 +00:00
|
|
|
|
|
|
|
<!ENTITY api.register.snippet '<para>
|
|
|
|
The php-function callback <parameter>function</parameter> can be either:
|
|
|
|
<itemizedlist>
|
|
|
|
<listitem><para>
|
|
|
|
A string containing the function <parameter>name</parameter>
|
|
|
|
</para></listitem>
|
|
|
|
|
|
|
|
<listitem><para>
|
|
|
|
An array of the form <literal>array(&$object, $method)</literal> with
|
|
|
|
<literal>&$object</literal> being a reference to an
|
|
|
|
object and <literal>$method</literal> being a string
|
|
|
|
containing the method-name
|
|
|
|
</para></listitem>
|
|
|
|
|
|
|
|
<listitem><para>
|
|
|
|
An array of the form
|
2006-10-16 16:13:53 +00:00
|
|
|
<literal>array($class, $method)</literal> with
|
2006-09-26 22:41:21 +00:00
|
|
|
<literal>$class</literal> being the class name and
|
|
|
|
<literal>$method</literal> being a method of the class.
|
|
|
|
</para></listitem>
|
|
|
|
</itemizedlist>
|
|
|
|
</para>'>
|