Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:84853
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain fischer.name from 62.179.121.49 cause and error)
Message-ID: <5505C22D.3010203@fischer.name>
Date: Sun, 15 Mar 2015 18:32:29 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <CAF+90c8fkaDu+xiCdQ2F6+MXMSyzvPkDcRjXCCs5YtEqpzsmZA@mail.gmail.com>
In-Reply-To: <CAF+90c8fkaDu+xiCdQ2F6+MXMSyzvPkDcRjXCCs5YtEqpzsmZA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Spam_score: -2.9
X-Spam_score_int: -28
X-Spam_bar: --
X-Spam_report: Spam detection software, running on the system "scanner01.home", has
 identified this incoming email as possible spam.  The original message
 has been attached to this so you can view it (if it isn't spam) or label
 similar future email.  If you have any questions, see
 the administrator of that system for details.
 
 Content preview:  On 15.03.15 16:46, Nikita Popov wrote: > To ensure we have
    no shortage of new RFC votes... > > https://wiki.php.net/rfc/reclassify_e_strict#vote
    > > Voting is open for ten days :) From the RFC: "Signature mismatch during
    inheritance ... Possible alternative: Convert to E_DEPRECATED, if we intend
    to make this a fatal error in the future. " [...] 
 
 Content analysis details:   (-2.9 points, 5.0 required)
 
  pts rule name              description
 ---- ---------------------- --------------------------------------------------
 -1.0 ALL_TRUSTED            Passed through trusted hosts only via SMTP
 -1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1%
                             [score: 0.0000]
Subject: Re: [PHP-DEV] [VOTE] Reclassify E_STRICT notices
From: markus@fischer.name (Markus Fischer)

On 15.03.15 16:46, Nikita Popov wrote:
> To ensure we have no shortage of new RFC votes...
> 
>     https://wiki.php.net/rfc/reclassify_e_strict#vote
> 
> Voting is open for ten days :)

From the RFC:

"Signature mismatch during inheritance
...
Possible alternative: Convert to E_DEPRECATED, if we intend to make this
a fatal error in the future.
"

Has there been any decision made which course to follow? I ask since I
don't see voting option for it (not saying it needs one!), it just would
be nice to carve in stone what's going to be done about it.

Otherwise good cleanup RFC IMHO, +1

- Markus