Re: [PHP-DEV] [RFC][DISCUSSION] Introduce scrpt_path

2015-02-08 Thread Rowan Collins
On 08/02/2015 09:03, Yasuo Ohgaki wrote: If this was a PHP_INI_PERDIR setting, then I wouldn't really mind as much. > >But as PHP_INI_USER, I don't like it at all. How about allow to set the ini only once during execution? Like open_baedir [1], it should probably be possible to *tighten* the

Re: [PHP-DEV] [RFC][DISCUSSION] Introduce scrpt_path

2015-02-08 Thread Yasuo Ohgaki
Hi Matthew, On Sat, Feb 7, 2015 at 5:29 AM, Matthew Leverton wrote: > On Fri, Feb 6, 2015 at 1:02 PM, Yasuo Ohgaki wrote: > > > > Basically, it's administrative solution. Application should set these > > setting > > or administrator should. > > > > Library shouldn't touch the setting, otherwise

Re: [PHP-DEV] [RFC][DISCUSSION] Introduce scrpt_path

2015-02-06 Thread Matthew Leverton
On Fri, Feb 6, 2015 at 1:02 PM, Yasuo Ohgaki wrote: > > Basically, it's administrative solution. Application should set these > setting > or administrator should. > > Library shouldn't touch the setting, otherwise they hit their own foot. > If this was a PHP_INI_PERDIR setting, then I wouldn't rea

Re: [PHP-DEV] [RFC][DISCUSSION] Introduce scrpt_path

2015-02-06 Thread Yasuo Ohgaki
Hi Leigh, On Sat, Feb 7, 2015 at 3:46 AM, Yasuo Ohgaki wrote: > >> >> I think this is a better solution than script{,_once}. I definitely >> prefer it over the previous RFC > > > I thought script()/script_once() is enough, but it's not. > There are modules uses custom script loaders, including p

Re: [PHP-DEV] [RFC][DISCUSSION] Introduce scrpt_path

2015-02-06 Thread Yasuo Ohgaki
Hi Matthew, On Sat, Feb 7, 2015 at 1:45 AM, Matthew Leverton wrote: > On Fri, Feb 6, 2015 at 6:02 AM, Yasuo Ohgaki wrote: > > https://wiki.php.net/rfc/script_path > > > > It's work in progress, but I would like to start discuss. > > > > I don't really like it; but I don't really like most INI-b

Re: [PHP-DEV] [RFC][DISCUSSION] Introduce scrpt_path

2015-02-06 Thread Yasuo Ohgaki
Hi Leigh, On Fri, Feb 6, 2015 at 9:53 PM, Leigh wrote: > On 6 February 2015 at 12:02, Yasuo Ohgaki wrote: > > Hi all, > > > > This RFC was renamed from "script() and script_once()". > > Original proposal had defect. It wasn't perfect. > > > > This RFC proposes "script_path" INI directive to eli

Re: [PHP-DEV] [RFC][DISCUSSION] Introduce scrpt_path

2015-02-06 Thread Matthew Leverton
On Fri, Feb 6, 2015 at 6:02 AM, Yasuo Ohgaki wrote: > https://wiki.php.net/rfc/script_path > > It's work in progress, but I would like to start discuss. > I don't really like it; but I don't really like most INI-based solutions. I agree that this is a problem with poorly written code, but at the

Re: [PHP-DEV] [RFC][DISCUSSION] Introduce scrpt_path

2015-02-06 Thread Leigh
On 6 February 2015 at 12:02, Yasuo Ohgaki wrote: > Hi all, > > This RFC was renamed from "script() and script_once()". > Original proposal had defect. It wasn't perfect. > > This RFC proposes "script_path" INI directive to eliminate > file/script inclusion at all via require(). > > https://wiki.ph

[PHP-DEV] [RFC][DISCUSSION] Introduce scrpt_path

2015-02-06 Thread Yasuo Ohgaki
Hi all, This RFC was renamed from "script() and script_once()". Original proposal had defect. It wasn't perfect. This RFC proposes "script_path" INI directive to eliminate file/script inclusion at all via require(). https://wiki.php.net/rfc/script_path It's work in progress, but I would like to