Re: exploring include_path options for pecl/phar

Hi Greg,

2b) design a more intelligent include_path parser that recognizes phar stream wrappers this would almost completely solve the problem, as it would then allow putting full phar:// stream paths inside include_path. No changes would need to be made to the PHP code, as interception of include_path-related stuff would happen inside pecl/phar. Can anyone think of a problem with 2b? I can't think of any and it is really ridiculously simple, but my intuition is nagging me that I am missing something that is a problem with this approach.

The only problem I can see with it is that it presumably means you'll need ext/phar enabled before you can use any pharballed application that isn't entirely standalone, is that correct? or could this interception magic be integrated into the default stub? - Steph