Hi Matteo, On Wed, Feb 11, 2015 at 12:48 PM, Yasuo Ohgaki <yohg...@ohgaki.net> wrote:
> On Tue, Feb 10, 2015 at 5:22 PM, Matteo Beccati <p...@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. > How about remove 2 INIs in the future with this RFC? script_embed=On/Off (New with this RFC) allow_url_include=On/Off I'll prepare patch that require(_once) string $filename [, int $include_type]; include(_once) string $filename [, int $include_type]; Where $include_type are - PHP_INCLUDE_DEFAULT (default: no embed, no URL) - PHP_INCLUDE_EMBED (allow embed) - PHP_INCLUDE_URL (allow URL) These types are combined like "PHP_INCLUDE_EMBED | PHP_INCLUDE_URL". Then, above 2 INIs may be deprecated and remove in the future. How about remove them by PHP 7.3. What do you think? Regards, -- Yasuo Ohgaki yohg...@ohgaki.net
