On 15.10.2019 at 10:27, Gert wrote:
> I may be a bit late to this party, but will the promotion to error
> exception of illegal offsets also happen for using resources as array
> keys? These currently produce a notice, and are then casted to an
> integer: https://3v4l.org/cQ8hf
> Or will the behav
I may be a bit late to this party, but will the promotion to error
exception of illegal offsets also happen for using resources as array
keys? These currently produce a notice, and are then casted to an
integer: https://3v4l.org/cQ8hf
Or will the behaviour of that remain the same?
On Fri, 11 Oct 2
> Le 11 oct. 2019 à 11:12, Olumide Samson a écrit :
>
> On Fri, Oct 11, 2019, 9:29 AM Benjamin Morel
> wrote:
>
>>>
>>> As people have expressed interest in hearing about direct technical
>>> benefits that these kinds of changes have ... let me give you an example
>>> that came up yesterday.
On Thu, Sep 26, 2019 at 4:31 AM Christian Schneider
wrote:
> Am 26.09.2019 um 09:41 schrieb Nikita Popov :
> > * Remainder: 54 yes, 3 no. Accepted with 95% majority.
>
> Just for the record:
> The one I'm most concerned about here is the foreach on undefined
> variables throwing an exception.
> W
Am 26.09.2019 um 09:41 schrieb Nikita Popov :
> * Remainder: 54 yes, 3 no. Accepted with 95% majority.
Just for the record:
The one I'm most concerned about here is the foreach on undefined variables
throwing an exception.
While this was already promoted to a warning at an earlier stage it still
Den 2019-09-18 kl. 21:44, skrev Claude Pache:
Le 18 sept. 2019 à 18:28, Nikita Popov a écrit :
I just realized that I missed one notice here, because it is generated from
a different location: "Constant %s already defined" (The define/const will
be ignored and the previous value used.)
It wou
> Le 18 sept. 2019 à 18:28, Nikita Popov a écrit :
>
> I just realized that I missed one notice here, because it is generated from
> a different location: "Constant %s already defined" (The define/const will
> be ignored and the previous value used.)
>
> It would be great to have that as an e
On Thu, Sep 12, 2019 at 10:13 AM Olumide Samson
wrote:
>
>
> On Thu, Sep 12, 2019, 2:59 PM Chase Peeler wrote:
>
>>
>>
>> On Thu, Sep 12, 2019 at 8:33 AM Olumide Samson
>> wrote:
>>
>>> Thanks to those who can vote, all in all I hope for a better language
>>> where
>>> we can proudly post jobs(
On Thu, Sep 12, 2019, 2:59 PM Chase Peeler wrote:
>
>
> On Thu, Sep 12, 2019 at 8:33 AM Olumide Samson
> wrote:
>
>> Thanks to those who can vote, all in all I hope for a better language
>> where
>> we can proudly post jobs(even intern) for on our company's website without
>> been looked down on
On Thu, Sep 12, 2019 at 8:33 AM Olumide Samson wrote:
> Thanks to those who can vote, all in all I hope for a better language where
> we can proudly post jobs(even intern) for on our company's website without
> been looked down on as inferior.
>
> If you're so embarrassed by the language, then wh
Thanks to those who can vote, all in all I hope for a better language where
we can proudly post jobs(even intern) for on our company's website without
been looked down on as inferior.
Since I can't vote, I can only hope for the best.
<3
On Thu, Sep 12, 2019, 1:17 PM Nikita Popov wrote:
> Hi in
Hi internals,
I've opened the vote on //wiki.php.net/rfc/engine_warnings.
There are 4 votes, all of them independent. The first 3 are for specific
cases that were controversial during the discussion, the last one is for
the remainder of the proposal.
Voting closes 2019-09-26.
Regards,
Nikita
12 matches
Mail list logo
