On Sun, 5 Apr 2020 at 16:01, Gabriel Caruso
wrote:
>
> Hello, internals.
>
> Hereby you can find the RFC Document that I want to discuss as suggested
> via https://externals.io/message/109416 and
> https://externals.io/message/107990:
>
> https://wiki.php.net/rfc/magic-methods-signature
>
> Best
Hi,
Máté Kocsis wrote:
Hi Internals,
Together with George, I'd like to propose an RFC for a long-standing
problem PHP has:
casting floats to string depends on the locale settings. As this behaviour
is nonsense, and
because it can cause quite serious problems, we would like to get rid of
On Wed, 15 Apr 2020 at 22:27, Derick Rethans wrote:
> On 15 April 2020 20:36:25 BST, "G. P. B."
> wrote:
> >On Wed, 15 Apr 2020 at 15:51, Derick Rethans wrote:
> >
> >> On Wed, 15 Apr 2020, Michał Brzuchalski wrote:
> >>
> >> > Hi internals,
> >> >
> >> > I hope you're doing well.
> >> >
> >>
On 15 April 2020 20:36:25 BST, "G. P. B." wrote:
>On Wed, 15 Apr 2020 at 15:51, Derick Rethans wrote:
>
>> On Wed, 15 Apr 2020, Michał Brzuchalski wrote:
>>
>> > Hi internals,
>> >
>> > I hope you're doing well.
>> >
>> > I'd like to announce the PHP Namespace in core RFC for discussion.
>> >
Hello all,
We've updated the implementation [1] and RFC [2] to provide a
temporary INI setting which will emit a warning every time a locale-aware
float to string conversation would have been done in PHP 7.
It's current name debug_local_sensitive_float_casts is also up to
debate and will be voted
On Wed, 15 Apr 2020 at 19:24, Andrea Faulds wrote:
> Hi,
>
> Michał Brzuchalski wrote:
> > Hi Marcio,
> >
> > śr., 15 kwi 2020 o 18:39 Marcio Almada
> napisał(a):
> >
> >> Even though I'm fond to the idea of languages having the official
> >> stdlib contained
> >> into a single space, there
On Wed, 15 Apr 2020 at 18:39, Marcio Almada wrote:
> >
> > Hi internals,
> >
> > I hope you're doing well.
> >
> > I'd like to announce the PHP Namespace in core RFC for discussion.
> > The RFC is authored by me together with George Peter Banyard and it's
> > purpose
> > is nothing more like to
On Wed, 15 Apr 2020 at 15:51, Derick Rethans wrote:
> On Wed, 15 Apr 2020, Michał Brzuchalski wrote:
>
> > Hi internals,
> >
> > I hope you're doing well.
> >
> > I'd like to announce the PHP Namespace in core RFC for discussion.
> > The RFC is authored by me together with George Peter Banyard
Hi!
> I'm not quite sure what the way forward regarding that is. I can understand
> the reluctance to propose the Rust-style block expression syntax, given its
Speaking of which, what is the problem with that? I mean, if we just
declare that the value of a block is the return of the last
Hi,
Michał Brzuchalski wrote:
Hi Marcio,
śr., 15 kwi 2020 o 18:39 Marcio Almada napisał(a):
Even though I'm fond to the idea of languages having the official
stdlib contained
into a single space, there seems to be no practicality on a \PHP namespace
usage
at this point IMMO.
We would be in
Hi Mark,
Mark Randall wrote:
As internals "claims" the top level namespace, this effectively means
that all userland code must exist in its own namespace, which is
indeed how almost all modern userland code is written, which if
anything this proves the benefit of namespacing.
Yes, post-5.3
Hi Derick,
śr., 15 kwi 2020 o 15:51 Derick Rethans napisał(a):
> On Wed, 15 Apr 2020, Michał Brzuchalski wrote:
>
> > Hi internals,
> >
> > I hope you're doing well.
> >
> > I'd like to announce the PHP Namespace in core RFC for discussion.
> > The RFC is authored by me together with George
Hi Marcio,
śr., 15 kwi 2020 o 18:39 Marcio Almada napisał(a):
> >
> > Hi internals,
> >
> > I hope you're doing well.
> >
> > I'd like to announce the PHP Namespace in core RFC for discussion.
> > The RFC is authored by me together with George Peter Banyard and it's
> > purpose
> > is nothing
>
> Hi internals,
>
> I hope you're doing well.
>
> I'd like to announce the PHP Namespace in core RFC for discussion.
> The RFC is authored by me together with George Peter Banyard and it's
> purpose
> is nothing more like to allow the use of PHP Namespace in the core.
>
> The RFC is described at
Hi Nikita
> I think part of the problem is that it's a case of either / or.
I agree that your example is an unpleasant limitation.
> I'm not quite sure what the way forward regarding that is. I can understand
> the reluctance to propose the Rust-style block expression syntax, given its
>
On Wed, 15 Apr 2020 at 12:57, Nikita Popov wrote:
> On Tue, Apr 14, 2020 at 7:45 PM Claude Pache
> wrote:
>
>>
>>
>> Le 14 avr. 2020 à 18:53, Nikita Popov a écrit :
>>
>> On Tue, Apr 14, 2020 at 6:07 PM Claude Pache
>> wrote:
>>
>>>
>>>
>>> > Le 14 avr. 2020 à 16:54, Nicolas Grekas
>>> a
On Wed, 15 Apr 2020, Michał Brzuchalski wrote:
> Hi internals,
>
> I hope you're doing well.
>
> I'd like to announce the PHP Namespace in core RFC for discussion.
> The RFC is authored by me together with George Peter Banyard and it's
> purpose
> is nothing more like to allow the use of PHP
On 15/04/2020 14:20, Remi Collet wrote:
Le 15/04/2020 à 13:21, Mark Randall a écrit :
Extension (pecl or other) can be include in core later
or core extension dropped and move to pecl.
Quoting the RFC:
Once approved, a namespace that is a child of \PHP will remain
exclusively for the
On Sun, Apr 12, 2020 at 2:16 AM Ilija Tovilo wrote:
> Hi internals
>
> I'd like to announce the match expression RFC that replaces the switch
> expression RFC I announced a few weeks ago.
> New: https://wiki.php.net/rfc/match_expression
> Old: https://wiki.php.net/rfc/switch_expression
>
> Due
Le 15/04/2020 à 13:21, Mark Randall a écrit :
> Greetings,
>
> I would like to re-open the discussion on properly reserving the \PHP
> namespace for the use of the engine and its core extensions.
What does that mean for PECL extension ?
If they have to use another namespace,
sorry, but I will
On Wed, 15 Apr 2020 at 14:29, Michał Brzuchalski <
michal.brzuchal...@gmail.com> wrote:
> Hi internals,
>
> I hope you're doing well.
>
> I'd like to announce the PHP Namespace in core RFC for discussion.
> The RFC is authored by me together with George Peter Banyard and it's
> purpose
> is
Hi internals,
I hope you're doing well.
I'd like to announce the PHP Namespace in core RFC for discussion.
The RFC is authored by me together with George Peter Banyard and it's
purpose
is nothing more like to allow the use of PHP Namespace in the core.
The RFC is described at
On 15/04/2020 12:40, Dan Ackroyd wrote:
Another benefit of having core PHP symbols in the root namespace is
that it means we can avoid having the discussion of what the namespace
naming rules should be. Again, the tradeoff of having to spend time on
that discussion of how to name things vs a
On 15/04/2020 12:23, Derick Rethans wrote:
This will mean that in a future version of PHP, some things will live in
a \PHP namespace, and others, such as DateTimeImmutable or Directory do
not. We should not be introducing inconsistencies.
It notes that it should be the preferred method for new
On Wed, 15 Apr 2020 at 12:21, Mark Randall wrote:
>
> Rather than seek to demand everything be moved into namespaces, I have
> instead written this RFC as something that would form a policy
> guideline for future development of the engine and those extensions
> which are directly managed by
Hi Mark,
On Wed, 15 Apr 2020, Mark Randall wrote:
> I would like to re-open the discussion on properly reserving the \PHP
> namespace for the use of the engine and its core extensions.
I will be voting no against this. The RFC states:
By design this RFC does NOT propose moving anything
Greetings,
I would like to re-open the discussion on properly reserving the \PHP
namespace for the use of the engine and its core extensions.
Rather than seek to demand everything be moved into namespaces, I have
instead written this RFC as something that would form a policy
guideline for future
Hi Andrea
> Well, I don't think we have any other expressions that are also
> statements with very slightly different syntax
The syntax isn't actually different. We don't have different grammar
for the match statement and expression. There's only one. Think of it
more like a type check. In other
On Tue, Apr 14, 2020 at 7:45 PM Claude Pache wrote:
>
>
> Le 14 avr. 2020 à 18:53, Nikita Popov a écrit :
>
> On Tue, Apr 14, 2020 at 6:07 PM Claude Pache
> wrote:
>
>>
>>
>> > Le 14 avr. 2020 à 16:54, Nicolas Grekas
>> a écrit :
>> >
>> > I'm just not sold on allowing "void" on __construct,
29 matches
Mail list logo
