Sara Golemon in php.internals (Tue, 20 Aug 2019 15:03:07 -0500):
>On Tue, Aug 20, 2019 at 1:58 PM Jan Ehrhardt wrote:
>
>> Derick Rethans in php.internals (Thu, 8 Aug 2019 09:53:28 +0100 (BST)):
>> >PHP 7.4.0beta2 has just been released and can be downloaded from:
>>
>> Was 7.4.0beta3 skipped?
On Tue, 20 Aug 2019 at 23:37, Rowan Tommins wrote:
>
> On 20/08/2019 22:18, Peter Kokot wrote:
> >> The approach was: add the deprecation notice in PHP 8, and remove short
> >> open tags in PHP 9 or PHP 10 (purposely left vague to get more support for
> >> the idea - as getting the deprecation
On 20/08/2019 22:18, Peter Kokot wrote:
The approach was: add the deprecation notice in PHP 8, and remove short open
tags in PHP 9 or PHP 10 (purposely left vague to get more support for the idea
- as getting the deprecation underway is the most important move).
I guess we should really
On Tue, 20 Aug 2019 at 19:47, Peter Bowyer wrote:
>
> On Tue, 20 Aug 2019 at 17:18, Peter Kokot wrote:
>>
>> Let's simplify this a bit because I'm not sure I have seen anyone
>> mentioning something like a PHP 10 milestone in all these discussions.
>> If we want to get rid of some feature like
On Tue, Aug 20, 2019 at 1:58 PM Jan Ehrhardt wrote:
> Derick Rethans in php.internals (Thu, 8 Aug 2019 09:53:28 +0100 (BST)):
> >PHP 7.4.0beta2 has just been released and can be downloaded from:
>
> Was 7.4.0beta3 skipped? 7.4.0beta4 is now tagged at Github.
>
On Tue, Aug 20, 2019 at 1:05 PM Влад Макин wrote:
> I would like to propose a little change in var_export function behavior.
> For today, this function returns string representation of array in old
> style with “array” keyword:
>
> var_export([]); // array()
>
> I think it would be better if the
Derick Rethans in php.internals (Thu, 8 Aug 2019 09:53:28 +0100 (BST)):
>PHP 7.4.0beta2 has just been released and can be downloaded from:
Was 7.4.0beta3 skipped? 7.4.0beta4 is now tagged at Github.
https://github.com/php/php-src/releases/tag/php-7.4.0beta4
--
Jan
--
PHP Internals - PHP
Greetings,
A week or so ago, G.P.B. submitted a pull request that contained a
declare that would automatically elevate certain errors to Error
exceptions (https://github.com/php/php-src/pull/4549).
As part of the discussion, Nikic stated the following:
"I believe it's okay to convert this
Hello!
I would like to propose a little change in var_export function behavior.
For today, this function returns string representation of array in old
style with “array” keyword:
var_export([]); // array()
I think it would be better if the function returned array representation in
modern square
On Tue, Aug 20, 2019 at 12:44 PM G. P. B. wrote:
> > This has been a topic of discussion in the past. The agreement was that
> > non-author edits are permitted if they are isolated to a clear
> > "counter-arguments" section. If someone had changed the meaning of the
> RFC
> > or of your
On Tue, 20 Aug 2019 at 17:18, Peter Kokot wrote:
> Let's simplify this a bit because I'm not sure I have seen anyone
> mentioning something like a PHP 10 milestone in all these discussions.
> If we want to get rid of some feature like this a very long timeline
> needs to be done and also major
2019年8月20日(火) 16:47 Rowan Tommins :
> On 20/08/2019 13:51, G. P. B. wrote:
> >- I seriously don't appreciate that the RFC has been edited*WITHOUT*
> my
> > knowledge to add endorsement names on the counterargument to the RFC on
> the
> > RFC itself when the appropriate place would have been
On 20/08/2019 17:56, Peter Kokot wrote:
Probably. But fact is that PHP opening short tags can be used. We can
enable them in controlled environments and use the short tags knowing
they will never be removed now. No deprecation warning is standing in
our way to do that now. And such code (or
On Tue, 20 Aug 2019 at 18:39, Rowan Tommins wrote:
>
> On 20/08/2019 17:18, Peter Kokot wrote:
> > About the docs - there are
> > very minor changes needed where "backwards compatibility" is mentioned
> > maybe. Because they are not in PHP for keeping BC anymore now. Nobody
> > proposed a better
On 20/08/2019 17:18, Peter Kokot wrote:
About the docs - there are
very minor changes needed where "backwards compatibility" is mentioned
maybe. Because they are not in PHP for keeping BC anymore now. Nobody
proposed a better solution than this RFC, then they are a feature.
Being "for
On Tue, 20 Aug 2019 at 18:02, Chase Peeler wrote:
>
> On Tue, Aug 20, 2019 at 11:50 AM Peter Kokot wrote:
>
> > On Tue, 20 Aug 2019 at 14:51, G. P. B. wrote:
> > >
> > > Hello internals,
> > >
> > > This RFC has been declined with 56% in favour (30/54) and 44% against
> > > (24/54).
> > >
> > >
On Tue, Aug 20, 2019 at 11:50 AM Peter Kokot wrote:
> On Tue, 20 Aug 2019 at 14:51, G. P. B. wrote:
> >
> > Hello internals,
> >
> > This RFC has been declined with 56% in favour (30/54) and 44% against
> > (24/54).
> >
> > Two side notes to this:
> >
> > - I seriously don't appreciate that
On Tue, 20 Aug 2019 at 14:51, G. P. B. wrote:
>
> Hello internals,
>
> This RFC has been declined with 56% in favour (30/54) and 44% against
> (24/54).
>
> Two side notes to this:
>
> - I seriously don't appreciate that the RFC has been edited *WITHOUT* my
> knowledge to add endorsement names
On Tue, Aug 20, 2019 at 7:51 AM G. P. B. wrote:
> - I seriously don't appreciate that the RFC has been edited *WITHOUT* my
> knowledge to add endorsement names on the counterargument to the RFC on the
> RFC itself when the appropriate place would have been the counter argument
> document.
>
>
On 20/08/2019 13:51, G. P. B. wrote:
- I seriously don't appreciate that the RFC has been edited*WITHOUT* my
knowledge to add endorsement names on the counterargument to the RFC on the
RFC itself when the appropriate place would have been the counter argument
document.
While I appreciate
Hello internals,
This RFC has been declined with 56% in favour (30/54) and 44% against
(24/54).
Two side notes to this:
- I seriously don't appreciate that the RFC has been edited *WITHOUT* my
knowledge to add endorsement names on the counterargument to the RFC on the
RFC itself when the
Hi internals@,
I'm Olumide Samson, lead developer at Zapay Inc(a financial service
provider).
All of our backend codes are written majorly in PHP(which is a language
i've been programming in since 2007) and C(since 2006) which i write
advance sys-related programs in...
I'm hoping i could
22 matches
Mail list logo
