Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:48669
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain seld.be designates 209.85.161.42 as permitted sender)
Message-ID: <4C0D022C.6000409@seld.be>
Date: Mon, 07 Jun 2010 16:29:00 +0200
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.5pre) Gecko/20100430 Lightning/1.0b2pre Thunderbird/3.1b2
MIME-Version: 1.0
To: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: stream_resolve_include_path improvement
From: j.boggiano@seld.be (Jordi Boggiano)

Heya,

stream_resolve_include_path [1] was introduced mostly to build framework
autoloaders. Good. It's great as it is. However it still forces the
framework to stash all its paths in the global include_path so that
they're picked up by that function.

Wouldn't it make sense to have an option, either via a third argument to
it, or as part of the context options maybe, to allow people to pass
their local include_path ?

That would mean one can ask php to resolve the path for file a.php
within array('/foo', '/bar'), without the need to alter the include_path
at all.

I'm thinking it could be handy for libs, but maybe I'm overlooking
something, is it already possible? Does it even makes sense
performance-wise?

Cheers

[1] http://ch2.php.net/stream_resolve_include_path

-- 
Jordi Boggiano
@seldaek :: http://seld.be/