Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:96231
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmx.de designates 212.227.17.20 as permitted sender)
To: Pascal KISSIAN <php-mailing-list@lool.fr>, internals@lists.php.net
References: <004101d21e33$124edf90$36ec9eb0$@lool.fr>
Message-ID: <3c80d975-7622-ec7c-481e-32a7599ebd5d@gmx.de>
Date: Tue, 4 Oct 2016 18:40:42 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.3.0
MIME-Version: 1.0
In-Reply-To: <004101d21e33$124edf90$36ec9eb0$@lool.fr>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: Feature Request: inline pseudo-instruction
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 04.10.2016 at 13:33, Pascal KISSIAN wrote:

> I have an application where a small file is included at multiple places.
> 
> So far so good.
> 
> The problem is that this include consists in a small piece of code which is
> inside a multi-level loop.
> 
> The include is done about an average of 100.000 times . 
> 
> When I manually replace the include with the code which is inside, the
> performance boost is about  a 50-100 factor.. 
> (with opcache enabled, it is far worst without opcache).
> 
> The problem is that if I make a change within the code, I do have to not
> forget to make changes a dozen of places...
> 
> Could it be possible to add a directive such as :
> 
> inline < filename >   
> 
> That includes  the file inline within the compiled pseudo code (at compile
> time) ... 
> 
> (it does not have a big importance for me that the target pseudo-code sets
> the line number of all inlined instructions to the line number of the inline
> directive)
> 
> Am I the only people needing this feature ?

If you really need this feature, I suggest that you're using a
preprocessor to prepare the files before they're compiled by PHP.  A
rather simple PHP script using preg_replace() might already be sufficient.

-- 
Christoph M. Becker