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
|
2005-05-23 15:43:01 +00:00
|
|
|
or result in non-sequential keys. This is unlike the
|
|
|
|
<ulink url="&url.php-manual;array_merge">array_merge()</ulink> function
|
2004-04-20 11:27:15 +00:00
|
|
|
of PHP which wipes out numerical keys and renumbers them.
|
|
|
|
</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
|
|
|
|
<link linkend="variable.compile.id">$compile_id</link>.
|
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
|
|
|
|
<link linkend="variable.compile.id">$compile_id</link> is when you
|
2005-05-23 15:43:01 +00:00
|
|
|
use more than one
|
|
|
|
<link linkend="variable.template.dir">$template_dir</link>
|
|
|
|
but only one
|
|
|
|
<link linkend="variable.compile.dir">$compile_dir</link>.
|
|
|
|
Set a separate <parameter>$compile_id</parameter> for each
|
|
|
|
<link linkend="variable.template.dir">$template_dir</link>, otherwise
|
2004-04-20 11:37:05 +00:00
|
|
|
templates of the same name will overwrite each other. You can
|
2005-05-23 15:43:01 +00:00
|
|
|
also set the $compile_id variable once
|
2004-04-20 11:37:05 +00:00
|
|
|
instead of passing this to each call to this function.
|
|
|
|
</para>'>
|