RE: [PEAR-DEV] include path solution?

On Wed, 2002-11-06 at 16:41, Lukas Smith wrote: > > From: Stig S. Bakken [mailto:ssb@fast.no] > > Sent: Wednesday, November 06, 2002 9:58 AM > > To: pear-dev@lists.php.net > > Subject: [PEAR-DEV] include path solution? > > > > Hi, > > > > During the PHP Conference in Frankfurt, Andi and I had a little talk > > about PEAR's include_path problems, and the solution we came up with > was > > simply to add separate functions for setting PHP's include_path. This > > may sound a bit odd, but we hope that ISPs that disable ini_set() for > > security reasons will not disable set_include_path(). We probably > > should mention it in the PHP release notes, and emphasize on the fact > > that setting include_path poses absolutely no security risk. > > > > I implemented {get,set,restore}_include_path() in the airport on the > way > > back from Frankfurt, they will be part of the PHP 4.3 release. > > > > I still prefer the constant solution because it gets rid of the include > path search. Besides eating performance I remember hearing one of the > bytecode folks mentioning that they also create issues with caching. > > Using the constant will of course require an upgrade to every PEAR > package, but its not a huge change and its easy to do with the pear > installer .. much easier than upgrading php ... Why would you want to use a constant? - Stig -- Stig Sæther Bakken, Fast Search & Transfer ASA, Trondheim, Norway http://pear.php.net/wishlist.php/ssb