Re: [RFC][DISCUSSION] Script only includes
| From: | Yasuo Ohgaki | Date: | Wed, 11 Feb 2015 03:48:03 +0000 |
| Subject: | Re: [RFC][DISCUSSION] Script only includes | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-82412@lists.php.net to get a copy of this message | ||
Hi Matteo,
On Tue, Feb 10, 2015 at 5:22 PM, Matteo Beccati <php@beccati.com> wrote:
> On 10/02/2015 01:52, Yasuo Ohgaki wrote:
>
>> Some of you are tired with this topic, but please take a look the RFC
>>
>> [RFC] Script only includes - this is 3rd version.
>> https://wiki.php.net/rfc/script_only_include
>>
>> Please let me know what you like or dislike.
>>
>
> I understand you goal, but ini settings are *bad*. We need less of them,
> not more.
>
> Developing applications or libraries that are resilient to all possible
> "variants" in the ini settings is painful. It's a waste of time for both
> users and developers trying to provide support.
I proposed script()/script_once() at first. Considering new names that
might
break existing apps, I choose INI.
The INI may be removed in the future, if include/require has an option. e.g.
require string $filename [, bool $embed_mode_flag];
Would you like me to include this change proposal in the RFC?
Even if we have embed_mode_flag, we are better to have the INI option for a
while for smooth migration.
Regards,
--
Yasuo Ohgaki
yohgaki@ohgaki.net