Hi!
PHPUnit 8 changed e.g. ` function setUp(){}` to ` function setUp():
void{} ` and a lot of people did not like being forced to do the same on
their `setUp()`.
The issue is not PHPUnit adding `void`, but PHP forcing `void` even when
it's not necessary. If PHPUnit wants to use void but in
Hi!
> Without a required discussion period, there could be slightly more
> 'incentive' for RFC authors to respond as quickly as possible, to 'get
> the discussion out the way'.
I see it exactly opposite - since we have no quorum requirement,
declaring the vote as soon as possible if a couple of p
Hi!
> 1. There is no required discussion period. However, if an RFC vote is
> opened without leaving enough time for discussion, then voters can and
> should vote the RFC down on the grounds of insufficient discussion.
I don't think this is a good idea. I see no scenario it improves -
there's not
Hi,
On 04.02.19 07:24, Remi Collet wrote:
Le 02/02/2019 à 20:24, Legale Legage a écrit :
These scripts are included to the standard deb/rpm packages
No, this is a deb only stuff
RPM installed = extension enabled.
Remi
P.S. I have never understand the need of such tools...
did it made sen
> Le 4 févr. 2019 à 04:22, Wes a écrit :
>
> Hello PHPeeps!
>
> Recent events convinced me to write this RFC :P
>
> Please have a read here https://wiki.php.net/rfc/allow-void-variance
>
> I am targeting all the supported PHP versions because this is mainly to
> placate the discontent that a
On 2/3/19 9:00 PM, Nikita Popov wrote:
> On Sun, Feb 3, 2019 at 5:16 PM Zeev Suraski wrote:
>
>>
>>> On 3 Feb 2019, at 16:43, Jan Ehrhardt wrote:
>>>
>>> Zeev Suraski in php.internals (Sun, 3 Feb 2019 11:02:56 +):
How is that related?
>>>
>>> It is directly related with your
On 2/1/19 7:30 PM, Larry Garfield wrote:
> On Friday, February 1, 2019 2:41:06 AM CST Dmitry Stogov wrote:
>> On 2/1/19 3:29 AM, Larry Garfield wrote:
>
>>> Question from a non-compiler-engineer: Could we end up in a situation
>>> where
>>> future language features (in 8.3 or something) are onl
On Sun, Feb 3, 2019 at 12:08 PM Nikita Popov wrote:
>
>> Personally, I find any proposal that does not deal with clearly defining
>> voting eligibility not only questionable, but a non-starter, that has no
>> parallels in any other major Open Source projects.
>>
>
> Why? While I think the questio
Hi,
Le 02/02/2019 à 20:24, Legale Legage a écrit :
> These scripts are included to the standard deb/rpm packages
No, this is a deb only stuff
RPM installed = extension enabled.
Remi
P.S. I have never understand the need of such tools...
did it made sense in previous century, where download h
Hello,
On Mon, 4 Feb 2019 at 02:03, Levi Morrison wrote:
>
> On Sun, Feb 3, 2019 at 5:15 PM azjezz wrote:
> >
> > Hello Internals !
> >
> > As @official_php suggested [1], I'm here to propose a new website for the
> > PHP Project.
> >
> > In my opinion, current design looks old, outdated and bl
Hello PHPeeps!
Recent events convinced me to write this RFC :P
Please have a read here https://wiki.php.net/rfc/allow-void-variance
I am targeting all the supported PHP versions because this is mainly to
placate the discontent that arised by PHPUnit enforcing its users to use
void, so waiting 7.
On Wed, 30 Jan 2019 at 13:57, Derick Rethans wrote:
>
> On Mon, 28 Jan 2019, Zeev Suraski wrote:
>
> >
> > > I would like to make two changes to this header:
> > >
> > > 1. Change "PHP Version 7" line to just "PHP", to avoid the necessity of
> > > updating this for
> > > new major versions. I don
On Sun, Feb 3, 2019 at 5:15 PM azjezz wrote:
>
> Hello Internals !
>
> As @official_php suggested [1], I'm here to propose a new website for the PHP
> Project.
>
> In my opinion, current design looks old, outdated and bland. This sadly may
> reflect "badly" on the language
>
> reputation nowaday
Hello Internals !
As @official_php suggested [1], I'm here to propose a new website for the PHP
Project.
In my opinion, current design looks old, outdated and bland. This sadly may
reflect "badly" on the language
reputation nowadays.
New comers find it hard to go around the website, to write
On Sun, 3 Feb 2019 at 18:39, David Rodrigues wrote:
>
> Hello everybody!
>
> The biggest problem that I see about this topic is the loss of performance,
Although performance impact might be a problem, my impression is that
PHP has some problems supporting method overloading that don't exist
in o
On 03.02.2019 at 20:05, Peter Kokot wrote:
> On Sun, 3 Feb 2019 at 20:00, Joe Watkins wrote:
>>
>> On a side note, at what point do we remove stuff from the manual/pecl, the
>> weakref is extension is dead, can't work with current versions of PHP, and
>> there was never a stable release ?
>>
>> I
Well there should be a:
overload function sum(float $b, float $b): float;
in that case or throw an error for no matching function available imho.
On Sun, Feb 3, 2019 at 8:00 PM Christoph M. Becker
wrote:
> On 03.02.2019 at 19:39, David Rodrigues wrote:
>
> > overload function sum(int $a, int $
I believe we can adopt the behaviour of mature languages that supports this
feature. Java, for instance, throw a compile-time error saying that the
method signature is ambiguous.
On Sun, Feb 3, 2019 at 17:51 David Rodrigues wrote:
> Em dom, 3 de fev de 2019 às 17:19, Rowan Collins
> escreveu:
>
On Sat, 2 Feb 2019 at 16:24, Nikita Popov wrote:
>
> What do you think?
> All RFCs must have a voting period of at least 14 days, announced in a
> separate [VOTE] thread.
That sounds mostly good to me. My feedback would be:
First, I wish people (including RFC authors) took more time to think
ab
On Sun, 3 Feb 2019 at 06:19, Zeev Suraski wrote:
>
> On Fri, Feb 1, 2019 at 7:14 PM Dan Ackroyd wrote:
>> Hi Zeev,
>>
>> Please can you very clearly state what problem you are trying to solve
>> by changing the rules about who can vote.
>
> Fair enough, I've heard that question from several other
Em dom, 3 de fev de 2019 às 17:19, Rowan Collins
escreveu:
> On 03/02/2019 19:00, Christoph M. Becker wrote:
> > On 03.02.2019 at 19:39, David Rodrigues wrote:
> >
> >> overload function sum(int $a, int $b): int;
> >> overload function sum(float $b, float $b): float;
> > Which function would sum(
On 03/02/2019 19:00, Christoph M. Becker wrote:
On 03.02.2019 at 19:39, David Rodrigues wrote:
overload function sum(int $a, int $b): int;
overload function sum(float $b, float $b): float;
Which function would sum(17.4, 42) call? Also consider:
sum(PHP_INT_MAX, PHP_INT_MAX)
vs.
sum(P
Hello,
On Sun, 3 Feb 2019 at 20:00, Joe Watkins wrote:
>
> Already taken care of :)
>
> On a side note, at what point do we remove stuff from the manual/pecl, the
> weakref is extension is dead, can't work with current versions of PHP, and
> there was never a stable release ?
>
> I'm not even sur
Already taken care of :)
On a side note, at what point do we remove stuff from the manual/pecl, the
weakref is extension is dead, can't work with current versions of PHP, and
there was never a stable release ?
I'm not even sure we have a mechanism to delete stuff from pecl ... there's
probably qu
On 03.02.2019 at 19:39, David Rodrigues wrote:
> overload function sum(int $a, int $b): int;
> overload function sum(float $b, float $b): float;
Which function would sum(17.4, 42) call? Also consider:
sum(PHP_INT_MAX, PHP_INT_MAX)
vs.
sum(PHP_INT_MAX+1, PHP_INT_MAX+1)
--
Christoph M. Be
On 03.02.2019 at 19:39, Joe Watkins wrote:
> Does that solve the problem for you Christoph ?
Yes, calling the class WeakReference would be fine for me.
--
Christoph M. Becker
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Updated patch, name is WeakReference.
Cheers
Joe
On Sun, 3 Feb 2019 at 19:39, Joe Watkins wrote:
> Does that solve the problem for you Christoph ?
>
> Cheers
> Joe
>
> On Sun, 3 Feb 2019 at 19:08, Robert Korulczyk wrote:
>
>>
>> > I can't really think of another name ... it's ... a weakref ...
Does that solve the problem for you Christoph ?
Cheers
Joe
On Sun, 3 Feb 2019 at 19:08, Robert Korulczyk wrote:
>
> > I can't really think of another name ... it's ... a weakref ...
>
> It is actually "weak reference", so why not WeakReference?
>
>
> Regards,
> Robert Korulczyk
>
Hello everybody!
I know that method overloading was discussed on past and because a lot of
reasons it was declined [1]. I think that it should be considered maybe for
PHP 8, but for now I would like to suggest a different implementation.
Because of a stronger support to parameter types that PHP h
> I can't really think of another name ... it's ... a weakref ...
It is actually "weak reference", so why not WeakReference?
Regards,
Robert Korulczyk
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Guys,
On 3.02.19 г. 18:16 ч., Zeev Suraski wrote:
On 3 Feb 2019, at 16:43, Jan Ehrhardt wrote:
Zeev Suraski in php.internals (Sun, 3 Feb 2019 11:02:56 +):
How is that related?
It is directly related with your statement that "developers with other
host OSs still use Linux for the act
On Sun, Feb 3, 2019 at 5:16 PM Zeev Suraski wrote:
>
> > On 3 Feb 2019, at 16:43, Jan Ehrhardt wrote:
> >
> > Zeev Suraski in php.internals (Sun, 3 Feb 2019 11:02:56 +):
> >>
> >>
> >> How is that related?
> >
> > It is directly related with your statement that "developers with other
> > hos
Afternoon Christoph,
I can't really think of another name ... it's ... a weakref ...
Probably using the PHP namespace makes most sense.
Cheers
Joe
On Sun, 3 Feb 2019 at 18:40, Christoph M. Becker wrote:
> On 02.02.2019 at 09:35, Joe Watkins wrote:
>
> > Some time ago I brought this up for dis
On 02.02.2019 at 09:35, Joe Watkins wrote:
> Some time ago I brought this up for discussion, and last night was reminded
> of it's existence, and so this morning rebased and reworked the patch a
> little based on the feedback I got back then.
>
> Since it was long ago, and there's no particular r
On Friday, February 1, 2019 7:11:40 PM CST Kalle Sommer Nielsen wrote:
> Den fre. 1. feb. 2019 kl. 02.42 skrev Larry Garfield
> > > So I would support a mechanism of some sort to give formal voting
rights
> > to
> > non-internals-C-developers who are still significant-PHP-contributors, as
> >
On Sunday, February 3, 2019 4:07:46 AM CST Nikita Popov wrote:
> On Sun, Feb 3, 2019 at 6:18 AM Zeev Suraski wrote:
> > The suggestion that the new RFC makes life more difficult, compared to the
> > current Voting RFC, is simply wrong. It is, in fact, very much the same -
> > except it's a lot m
> On 3 Feb 2019, at 16:43, Jan Ehrhardt wrote:
>
> Zeev Suraski in php.internals (Sun, 3 Feb 2019 11:02:56 +):
>>
>>
>> How is that related?
>
> It is directly related with your statement that "developers with other
> host OSs still use Linux for the actual PHP development". They don't u
On 03/02/2019 02:44, Walter Parker wrote:
If you can make it work on MacOS, Windows, and the BSDs, then great.
Otherwise, it should be left to the Linux distributions.
And bare in mind that there are a number of different standards
CURRENTLY used across the different LINUX distributions! The q
On 03/02/2019 06:51, Zeev Suraski wrote:
While this is anecdotal, I think you might find a different perspective from
user group organizers. I've encountered many user group members over the years
who run PHP on Windows. It's more common that they develop on Windows and
deploy to Linux, but I
Zeev Suraski in php.internals (Sun, 3 Feb 2019 11:02:56 +):
>Jan Ehrhardt in php.internals (Sun, 03 Feb 2019 11:47:09 +0100):
>>Hi Zeev,
>>
>>Zeev Suraski in php.internals (Sun, 3 Feb 2019 07:05:49 +):
>>>2. Most PHP production workloads are on Linux, and as far as I can tell
>>>this trend
On 3 Feb 2019, at 12:47, Jan Ehrhardt
mailto:php...@ehrhardt.nl>> wrote:
Hi Zeev,
Zeev Suraski in php.internals (Sun, 3 Feb 2019 07:05:49 +):
2. Most PHP production workloads are on Linux, and as far as I can tell
this trend is only growing over the years - with virtual machines and
now c
Hi Zeev,
Zeev Suraski in php.internals (Sun, 3 Feb 2019 07:05:49 +):
>2. Most PHP production workloads are on Linux, and as far as I can tell
>this trend is only growing over the years - with virtual machines and
>now containers becoming more and more popular - meaning that even
>developers w
On Sun, Feb 3, 2019 at 6:18 AM Zeev Suraski wrote:
>
>
> > -Original Message-
> > From: Nikita Popov
> > Sent: Saturday, February 2, 2019 6:24 PM
> > To: PHP internals
> > Subject: [PHP-DEV] Alternative voting reform: Streamlining the RFC
> process
> >
> > Hi internals,
> >
> > After di
> Am 03.02.2019 um 06:18 schrieb Zeev Suraski :
>
>> -Original Message-
>> From: Nikita Popov
>> Sent: Saturday, February 2, 2019 6:24 PM
>> To: PHP internals
>> Subject: [PHP-DEV] Alternative voting reform: Streamlining the RFC process
>>
>> Hi internals,
>>
>> After discussing the to
On Sat, Feb 2, 2019 at 10:20 PM Zeev Suraski wrote:
> On Fri, Feb 1, 2019 at 7:14 PM Dan Ackroyd wrote:
>
> > On Thu, 31 Jan 2019 at 13:44, Zeev Suraski wrote:
> > >
> > > Without further ado, an RFC that’s attempting to comprehensively solve
> > many of the issues that have plagued our RFC pro
45 matches
Mail list logo
