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
|
|
|
|
|
or result in non-sequential keys. This is unlike the array_merge() function
|
|
|
|
|
of PHP which wipes out numerical keys and renumbers them.
|
|
|
|
|
</para>
|
|
|
|
|
</note>'>
|
2004-04-20 11:37:05 +00:00
|
|
|
|
|
|
|
|
<!ENTITY parameter.compileid '<para>
|
|
|
|
|
As an optional third parameter, you can pass a <parameter>compile_id</parameter>.
|
|
|
|
|
This is in the event that you want to compile different versions of
|
|
|
|
|
the same template, such as having separate templates compiled
|
|
|
|
|
for different languages. Another use for compile_id is when you
|
|
|
|
|
use more than one $template_dir but only one $compile_dir. Set
|
|
|
|
|
a separate <parameter>compile_id</parameter> for each $template_dir, otherwise
|
|
|
|
|
templates of the same name will overwrite each other. You can
|
|
|
|
|
also set the <link
|
|
|
|
|
linkend="variable.compile.id">$compile_id</link> variable once
|
|
|
|
|
instead of passing this to each call to this function.
|
|
|
|
|
</para>'>
|
