Hi Paul,
niedz., 15 wrz 2019 o 15:48 Paul M. Jones napisał(a):
>
>
> > On Sep 12, 2019, at 09:00, Michał Brzuchalski <
> michal.brzuchal...@gmail.com> wrote:
> >
> > Hi internals,
> >
> > I'd like to open discussion about RFC: Object Initializer.
> >
> > This proposal reduces boilerplate of obje
Hello Mike,
On Mon, Sep 16, 2019 at 3:50 AM Mike Schinkel
wrote:
> Hi all,
>
> I am relatively new to discussions on the list, and so I have tried to
> understand the ethos of the community to stay within bounds that the
> community generally considers acceptable.
>
> However I am realizing thos
Hi Internals
I don't have permission to create RFCs but I would like to propose/discuss
new language construct called `ifset()` which is syntactic sugar to null
coalescing operator with rhs value `null`. The goal of this proposal is
similar to Andrea Fauld's proposal (
https://wiki.php.net/rfc/una
Hi Joe
Den søn. 15. sep. 2019 kl. 08.48 skrev Joe Watkins :
>
> Morning internals,
>
> There is confusion among the community, and contained in the documented
> history of PHP on the wider internet.
>
> The Wikipedia states that PHP is developed by the PHP Group, in saying this
> it is (must be) r
> On Sep 14, 2019, at 4:47 PM, Rowan Tommins wrote:
> I think that's only true because you've actually proposed a number of related
> but different features.
See my other email to the list asking about what is in-bounds and what it
out-of-bounds regarding RFC discussion.
I seemed logical to
On Sun, 2019-09-15 at 18:11 +0100, Dan Ackroyd wrote:
> HI internals,
>
> Currently, it is quite difficult to signup to get a PECL account.
>
> We have a somewhat deliberately obtuse form to signup through, which
> then needs to be manually approved by someone with the appropriate
> karma.
I thi
Hi all,
I am relatively new to discussions on the list, and so I have tried to
understand the ethos of the community to stay within bounds that the community
generally considers acceptable.
However I am realizing those the bound of acceptability may be fluid at times
so I am asking explicitl
On Fri, Mar 22, 2019 at 9:14 PM Benjamin Eberlei
wrote:
> Hi Internals,
>
> Thomas and I are working on updating the ext/dom to add support for the
> current DOM Living Standard API as standardized here:
> https://dom.spec.whatwg.org/
>
> https://wiki.php.net/rfc/dom_living_standard_api
>
> This
On 9/15/2019 10:11 AM, Dan Ackroyd wrote:
HI internals,
Currently, it is quite difficult to signup to get a PECL account.
We have a somewhat deliberately obtuse form to signup through, which
then needs to be manually approved by someone with the appropriate
karma.
Over the past year two people
On 28/08/2019 10:33, Nikita Popov wrote:
https://wiki.php.net/rfc/engine_warnings
I am 100% behind the exception proposals, however I did want to discuss
the warnings.
I am personally of the belief that there should be a distinction made
between notices / warnings issued by the engine, and
> > On Sep 15, 2019 at 8:57 AM,wrote: > >
Anyone may initiate an RFC for any subject. > For example, this phrasing
means the RFC system itself can be put up to vote, to be removed and replaced
with something entirely non-democratic. I do not want dive too deep into this
deb
On Sun, Sep 15, 2019, 11:41 PM Olumide Samson wrote:
>
>
> On Sun, Sep 15, 2019, 8:33 PM Stanislav Malyshev
> wrote:
>
>> Hi!
>>
>> > Does anyone object to any of those words ?
>>
>> Yes. I do not think precommitting to implement anything that has been
>> put on wiki and passed the vote is a goo
Not super familiar with building PHP, but this should be a reasonable
starting point, tested on a fresh install of Ubuntu 18.04.3:
apt install -y autoconf gcc bison re2c libxml2-dev libssl-dev
libsqlite3-dev libcurl4-openssl-dev libpng-dev libwebp-dev libjpeg-dev
vflib3-dev libc-client-dev libkrb5
On 15/09/2019 21:53, Gabriel Caruso wrote:
The main problem with Docker and php-src is that we need to touch the OS in
order to make sure the new features and bugfixes will be compatible.
What in particular needs to be adjusted at OS level to make testing
work? If there's a list we can probabl
On 15-09-19 22:53, Gabriel Caruso wrote:
>
>
> The main problem with Docker and php-src is that we need to touch the OS in
> order to make sure the new features and bugfixes will be compatible.
>
> Docker create a layer on top of that, right?
>
Correct. Honestly I was not considering the use c
Hi!
> May I suggest to provide instructions to build using Docker? This has a
> number of advantages:
>
> * Same instructions will work on Linux, MacOS and Windows
> * No need to install build dependencies on your host
> * Spin up a MySQL container by running 'docker run mysql:version'
This is c
Hello Dik
On Sun, Sep 15, 2019, 22:42 Dik Takken wrote:
> On 15-09-19 20:49, Nikita Popov wrote:
> >
> > Anyone interested in doing this?
> >
>
> Hi Nikita,
>
> May I suggest to provide instructions to build using Docker? This has a
> number of advantages:
>
> * Same instructions will work on Li
On 15-09-19 20:49, Nikita Popov wrote:
>
> Anyone interested in doing this?
>
Hi Nikita,
May I suggest to provide instructions to build using Docker? This has a
number of advantages:
* Same instructions will work on Linux, MacOS and Windows
* No need to install build dependencies on your host
Hi!
> Then we should undo all changes (as far as possible) caused by the RFCs
> listed in the Process and Policy section[1], probably starting with the
> Voting (aka. RFC) process RFC itself, which by the way, states as
> introduction since its very first version from 2011 (emphasis mine):
>
> |
On 15.09.2019 at 21:33, Stanislav Malyshev wrote:
>> Do we need to vote on changing the introduction (I'm happy to start an rfc
>> for this, if necessary) ?
>
> I don't think RFCs were meant to essentially remake all project
> governance structure. They were meant for solving technical questions,
Hi!
> Does anyone object to any of those words ?
Yes. I do not think precommitting to implement anything that has been
put on wiki and passed the vote is a good thing. Its a good conflict
resolution mechanism when we're talking about where or not to implement
certain technical feature. But IMO it
Hi,
Our build instructions in
https://github.com/php/php-src#building-php-source-code are currently a bit
bare... they show the basic "./buildconf && ./configure && make" cycle, but
everyone who actually tries this will quickly find out that there is a lot
more to building PHP...
Every time I com
On Sun, Sep 15, 2019 at 7:39 PM Gabriel Caruso
wrote:
> Hello Nikita,
>
> Em dom, 15 de set de 2019 às 19:29, Nikita Popov
> escreveu:
>
>> Hi,
>>
>> gcov.php.net used to provide valgrind reports and code coverage for
>> php-src. It no longer works with 7.4/8.0, because the OS is very old, and
>
Hello Nikita,
Em dom, 15 de set de 2019 às 19:29, Nikita Popov
escreveu:
> Hi,
>
> gcov.php.net used to provide valgrind reports and code coverage for
> php-src. It no longer works with 7.4/8.0, because the OS is very old, and
> building new versions of PHP there gets very hard. The valgrind rep
Hi,
gcov.php.net used to provide valgrind reports and code coverage for
php-src. It no longer works with 7.4/8.0, because the OS is very old, and
building new versions of PHP there gets very hard. The valgrind reports
have essentially been subsumed by asan/ubsan on Azure Pipelines, but we're
still
HI internals,
Currently, it is quite difficult to signup to get a PECL account.
We have a somewhat deliberately obtuse form to signup through, which
then needs to be manually approved by someone with the appropriate
karma.
Over the past year two people who I know from the community have
reached
On Sun, Sep 15, 2019, 17:28 Zeev Suraski wrote:
> I think it's clear you don't realize how rude you are, no surprises there.
> I'm not going to continue discussing this topic with you. You seem to
> think my words carry no weight, I'm absolutely sure yours don't carry any
> weight - let's save e
I think it's clear you don't realize how rude you are, no surprises there.
I'm not going to continue discussing this topic with you. You seem to
think my words carry no weight, I'm absolutely sure yours don't carry any
weight - let's save everyone some time mental strain.
To everyone else - I sta
On Sun, 15 Sep 2019 at 15:08, Zeev Suraski wrote:
> On Sun, Sep 15, 2019 at 4:44 PM Dan Ackroyd wrote:
>>
>>
>> It is not appropriate.
>>
>> If it continues, we are going to have to look at bringing in a code of
>> conduct to prevent this disruptive behaviour from being such a
>> negative effect
> On Sep 12, 2019, at 09:00, Michał Brzuchalski
> wrote:
>
> Hi internals,
>
> I'd like to open discussion about RFC: Object Initializer.
>
> This proposal reduces boilerplate of object instantiation and properties
> initialization in case of classes without required constructor arguments a
On Sun, 15 Sep 2019 at 14:16, Zeev Suraski wrote:
>
> We a new mechanism for deprecations/radical changes
The current maintainers are not bound by choices made by other people,
years ago.
No-one wants to break stuff just for the sake of it, but we are free
to correct mistakes that were made in t
On Sun, Sep 15, 2019 at 2:37 PM Peter Bowyer
wrote:
> On Sun, 15 Sep 2019 at 06:48, Joe Watkins wrote:
>
> > The Wikipedia states that PHP is developed by the PHP Group, in saying
> this
> > it is (must be) referring to internals as a whole, but our own
> > documentation names members of the gro
On Sun, 15 Sep 2019 at 13:57, Paul M. Jones wrote:
> Some things simply have to be off limits. What are those things?
PHP doesn't currently have a constitution, so currently voting is the
only way of deciding things. Also how we vote is one of the things
that people are allowed to vote on.
Eve
Hi all,
> Does anyone object to any of those words ?
This strikes me as yet another attempt at a power grab, so many of the words
are objectionable. However, this phrase will serve to show the weakness of the
proposal:
> Anyone may initiate an RFC for any subject.
There needs to be an artic
On Sun, Sep 15, 2019 at 1:15 PM Olumide Samson wrote:
> I also don't agree with the index and all its statistics
>
I'm not sure what you mean by 'all its statistics'. Mostly everything on
the methodology page is fluff, which may be purposely there to hide the
only part that really matters:
On Sun, 15 Sep 2019 at 06:48, Joe Watkins wrote:
> The Wikipedia states that PHP is developed by the PHP Group, in saying this
> it is (must be) referring to internals as a whole, but our own
> documentation names members of the group - who aren't even around mostly.
>
> I think we need to clarif
I'm not going to go into my opinions on rankings - others have already
done enough of that. I concur with them - most rankings are meaningless.
PHP is also not, in my opinion, dead or dying. It doesn't enjoy the
monopoly it once had on web-based development, but it's also still very
popular.
I also don't agree with the index and all its statistics, yet I'm not
invalidating it as it is a much-viewed index globally.
Though, what caught my eyes was this quote which I thought would be obvious
and Mike would have based those fact replies on(Yet I'm also not
invalidating his facts list and
On Sun, Sep 15, 2019 at 6:33 AM Mike Schinkel
wrote:
> > On Sep 14, 2019, at 5:18 PM, Olumide Samson
> wrote:
> >
> > https://jaxenter.com/php-tiobe-sept-2019-162096.html
> > I think this is one of those things we get from voting no...
> >
> > I might be wrong anyways :-?
>
First of all, Olumid
39 matches
Mail list logo
