Re: Re: Deprecating all INI set/get functions and use ini_set/get()
| From: | Yasuo Ohgaki | Date: | Wed, 28 Jan 2015 06:55:44 +0000 |
| Subject: | Re: Re: Deprecating all INI set/get functions and use ini_set/get() | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-81287@lists.php.net to get a copy of this message | ||
Hi Stas,
On Wed, Jan 28, 2015 at 4:48 AM, Stanislav Malyshev <smalyshev@gmail.com>
wrote:
> >>> Cons
> >>> - Existing code modifications. (It's E_DEPRECATED. User may ignore.)
> >>> - (Please point it out more disadvantages)
>
> I think removing or disrupting functions without a very good reason
> (such as, functionality going away or this function is abused or is
> broken in many use cases) is wrong. These functions don't seem broken,
> they just do something that you can do in another way. I don't think it
> is necessary to deprecated them.
I was about to add more of these functions for consistency indeed. e.g.
session_set_serialize_handler()
I changed my mind after discussion with Andrey. He insisted ini_set/get()
provides more consistency
and user friendliness. And I agreed with him.
There may be people like me and PHP may not need more simple ini_set/get()
copy functions.
What do you think about CODING_STANDARD part?
Regards,
--
Yasuo Ohgaki
yohgaki@ohgaki.net