mirror of
				https://github.com/smarty-php/smarty.git
				synced 2025-10-31 12:21:36 +01:00 
			
		
		
		
	
		
			
				
	
	
		
			29 lines
		
	
	
		
			1.3 KiB
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
			
		
		
	
	
			29 lines
		
	
	
		
			1.3 KiB
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
| <!-- $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
 | |
|   <ulink url="&url.php-manual;array_merge">array_merge()</ulink> function
 | |
|   of PHP which wipes out numerical keys and renumbers them.
 | |
|  </para>
 | |
| </note>'>
 | |
| 
 | |
| <!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
 | |
|  <parameter>$compile_id</parameter> is when you 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
 | |
|  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>'>
 |