Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:74708 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 77531 invoked from network); 3 Jun 2014 12:46:06 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 3 Jun 2014 12:46:06 -0000 Authentication-Results: pb1.pair.com header.from=narf@devilix.net; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=narf@devilix.net; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain devilix.net designates 209.85.215.45 as permitted sender) X-PHP-List-Original-Sender: narf@devilix.net X-Host-Fingerprint: 209.85.215.45 mail-la0-f45.google.com Received: from [209.85.215.45] ([209.85.215.45:39854] helo=mail-la0-f45.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 08/E1-64944-B83CD835 for ; Tue, 03 Jun 2014 08:46:05 -0400 Received: by mail-la0-f45.google.com with SMTP id s18so1478694lam.32 for ; Tue, 03 Jun 2014 05:46:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=devilix.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=lg5kMY+E3vebRfV+/1WDC4666xkkenCLHwCpXiYJQV4=; b=J+Lk/33H1VZkz/nctg6yLiT4+r/NKGLVgsaxg+itHISB/T4zxqTVPX0ftxu4ObkJ5s I3AzWJcwxJZLLqx2OMak9NeDxBVd7zhdgMiaxtHzYEGZ7Ckk1l9/PBVaVb6TDfLlWAZj FqaGelYTtBiPrVImgSPhZ2L8rN0YfR5WtaMNU= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=lg5kMY+E3vebRfV+/1WDC4666xkkenCLHwCpXiYJQV4=; b=GcU9OMpBJ4TfG/JzpGtdzzyBZDfkZyCpT9E1YZKrila7RHtmCQc5tTWLLSEyzq2yYI CHyC2RZeaRrgBlZoIl8wLLmCovJ5+Aba9qHaWykOGjUBn6E+MERuxaQIN4CSz6TPZ4M7 GYeAEQjqCiti7n8RL8tGNmemen6Fn2piLhRcKO2xmdWTYuh57he+nMkh3+0ZBouEApmN elpecQIqbT7wvyYGoQ6jvKlLy7E5vh+UizRg2yl0dMaxZ4POcfX9wg2WvpGxWxyXh2mC wvgZsnXKNI1WD5p5tHx8ftNcJbvYgcHRh9q9irp3TpeNHCndGJAe+rFRKI2bDyZjhqsp 9x7w== X-Gm-Message-State: ALoCoQlGWwUBPDt2bwiTOVZSol5UTihqUXQns+Vb5IMnGqO6gJcAto6t0OF/iUuaUMhpFzZv5EPO MIME-Version: 1.0 X-Received: by 10.112.33.83 with SMTP id p19mr1859418lbi.90.1401799560807; Tue, 03 Jun 2014 05:46:00 -0700 (PDT) Received: by 10.152.115.142 with HTTP; Tue, 3 Jun 2014 05:46:00 -0700 (PDT) In-Reply-To: References: Date: Tue, 3 Jun 2014 15:46:00 +0300 Message-ID: To: Ferenc Kovacs Cc: PHP Internals Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] question regarding #67309 From: narf@devilix.net (Andrey Andreev) Hi, On Tue, Jun 3, 2014 at 3:30 PM, Ferenc Kovacs wrote: > > > > On Tue, Jun 3, 2014 at 1:01 PM, Andrey Andreev wrote: >> >> On Tue, Jun 3, 2014 at 10:41 AM, Ferenc Kovacs wrote: >> > Hi, >> > >> > I wanted to ask what's our current consensus about feature requests li= ke >> > this: https://bugs.php.net/bug.php?id=3D67309 >> > The requested function wouldn't provide anything which isn't currently >> > available via ini_get(), but it would be a bit natural to expect a get >> > method where a set exists. >> > >> > -- >> > Ferenc Kov=C3=A1cs >> > @Tyr43l - http://tyrael.hu >> >> Hi, >> >> We talked about this with Yasuo in regards to some ext/session stuff >> (although it was about setters) and agreed on keeping ini_set() only. >> He even wrote a quick RFC about it: >> https://wiki.php.net/rfc/deprecate-ini-functions >> > > Yeah, but AFAIR we didn't come up with an agreement (other than reverting > out a couple of new functions from PHP 5.6.0). We didn't indeed, I was just giving you partial feedback. :) >> My opinion in general is that we don't need functions that duplicate >> ini_set(), ini_get() for a particular setting and existing ones should >> be removed in the future instead of adding more to complement them. No >> idea what other people think about it though. > > > I agree that providing multiple ways to achive the same thing is not real= ly > useful. > But we also have to decide whether or not it is worth the BC to remove so= me > existing function only because one can already do the same thing via > ini_set. With work supposedly being started on PHP6, now is the right time to make that decision. :) > Another (albeit maybe a bit far-fetched) aspect is that somebody could > assume that he/she can restrict a setting via disabling the appropriate > function(via disable_functions) while that can be bypassed through the > ini_set or vica versa. > So the more ways we provide for the same setting to be set it is more lik= ely > that somebody forgets protecting one of those. Exactly. Cheers, Andrey.