Re: [SMARTY-DEV] Inlining plugins/modifiers

From: Date: Thu, 22 May 2003 15:49:26 +0000
Subject: Re: [SMARTY-DEV] Inlining plugins/modifiers
References: 1 2 3 4 5 6 7  Groups: php.smarty.dev 
Request: Send a blank email to php-smarty-dev+get-1492@lists.php.net to get a copy of this message
> > the difference between inline code and code sitting in an external file > > is ONLY opening the file, reading it, and closing it... not more... > > There is a difference... the code gets duplicated instead of reused, and > the file sizes grow larger. So which is going to be better? The presence > of an accelerator and disk/memory space is going to play a factor. yes... you're definitely right... I just wanted to explain the difference at the time PHP executes the script... it first puts the complete code together, from the various includes() etc, and then transforms it into byte code... so there, the only difference is the inclusion, i.e. the reading of the file. sure, it's better to have the plugins in their seperate directory and loaded on demand... I'm against inline plugins, too :) David

« previous php.smarty.dev (#1492) next »