Re: [RFC] prepend_include_path()/append_include_path()
| From: | Markus Fischer | Date: | Thu, 14 Feb 2008 09:34:07 +0000 |
| Subject: | Re: [RFC] prepend_include_path()/append_include_path() | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-35489@lists.php.net to get a copy of this message | ||
Lukas Kahwe Smith wrote:
On 14.02.2008, at 10:20, Markus Fischer wrote:Fair enough. I think I feel pretty lucky that I've never had to operate in such environments ... On the other hand I feel unqualified taking a position here either then :) thanks, - MarkusPersonally I never understood why we've set_include_path in the first place anyway. "ini_set('include_path', ..." does exactly the same and the C function does actually exactly this.Short history lesson: The reason for set_include_path() is that many shared hosters disable ini_set(), yet many libraries/apps depend on users being able to control their include path.