[PHP-DEV] PHP 7.3 zif_handler changes

"Christoph M. Becker" in php.internals (Thu, 21 Jun 2018 12:28:49 +0200): >For more information on the new features and other changes, you can read >the NEWS file >(), or the >UPGRADING file >(

Re: [PHP-DEV] PHP 2^3

On 06/25/2018 07:13 AM, Johannes Schlüter wrote: On Mo, 2018-06-25 at 12:30 +, Zeev Suraski wrote: 3. Foreign Function Interface support. Related to this on a non-PHP-code and strategic matter I would like to rethink PECL. Currently maintenance and installing extensions using it is a pita.

Re: [PHP-DEV] PHP 2^3

On 25/06/2018 21:42, Larry Garfield wrote: What will definitely bring benefit to real world workloads is preloading, which (if we manage to do it) will dramatically reduce the per-request initialization stage. It could bring us much of the benefit of async-IO long running processes without sacri

RE: [PHP-DEV] PHP 2^3

> -Original Message- > From: Larry Garfield [mailto:la...@garfieldtech.com] > Sent: Monday, June 25, 2018 11:43 PM > To: internals@lists.php.net > Subject: Re: [PHP-DEV] PHP 2^3 > > That's certainly a good argument for the people doing deep engine work to > focus on that, but there's ample

Re: [PHP-DEV] PHP 8 next?

On 25/06/2018 20:34, Michael Morris wrote: So, about that Ternary operator? My understanding is that major releases are the only ones allowed to have breaking changes. Correcting the ternary operator to work like it does in all other languages is a small example. I don't think it's a good ide

Re: [PHP-DEV] PHP 2^3

On Monday, June 25, 2018 2:12:22 PM CDT Zeev Suraski wrote: > > When we speak of "typical web loads" not getting much benefit here, are we > > really talking about CGI-style "reboot every request" type loads rather > > than > > "IO-bound work"? Because it's been observed many times in the past t

Re: [PHP-DEV] PHP 8 next?

On 25/06/2018 19:54, Zeev Suraski wrote: On Mon, Jun 25, 2018 at 8:40 PM Chase Peeler wrote: 1.) Old code breaks during minor updates. We upgraded to 7.0 AFTER 7.1 was released, because we had already made major updates to upgrade to 7.0, and 7.1 introduced a few things that would have broken

Re: [PHP-DEV] PHP 2^3

> On Jun 25, 2018, at 7:30 AM, Zeev Suraski wrote: > > > 2. Better support long-running, async-based, microservices-focused execution > model. It's probably no secret that one of the key reasons Node is gaining > popularity is because it can handle a huge number of concurrent connections >

Re: [PHP-DEV] PHP 8 next?

On Mon, Jun 25, 2018 at 2:55 PM Zeev Suraski wrote: > On Mon, Jun 25, 2018 at 8:40 PM Chase Peeler > wrote: > > > 1.) Old code breaks during minor updates. We upgraded to 7.0 AFTER 7.1 > was > > released, because we had already made major updates to upgrade to 7.0, > and > > 7.1 introduced a few

Re: [PHP-DEV] [RFC] Deprecations for PHP 7.3

On Sun, Jun 24, 2018 at 11:47 AM, Nikita Popov wrote: > https://wiki.php.net/rfc/deprecations_php_7_3 > > Undocumented mbstring function aliases > Yeah, if they're just dumb aliases, then it's a slight gain to narrow the symbol table by removing duplicates. A modest composer package (nay, include

Re: [PHP-DEV] PHP 2^3

On Mon, Jun 25, 2018 at 8:52 PM Larry Garfield wrote: > On Monday, June 25, 2018 11:16:31 AM CDT Sara Golemon wrote: > > > > First, I'll admit that there's definitely some of that happening. But > to > > > paraphrase my daughters - "I didn't start it!". In other words - > people > > > are very

Re: [PHP-DEV] PHP 8 next?

On Mon, Jun 25, 2018 at 8:40 PM Chase Peeler wrote: > 1.) Old code breaks during minor updates. We upgraded to 7.0 AFTER 7.1 was > released, because we had already made major updates to upgrade to 7.0, and > 7.1 introduced a few things that would have broken our code - we didn't > have time to fi

Re: [PHP-DEV] [RFC] Deprecations for PHP 7.3

Hi! > There are multiple bug reports regarding strip_tags()'s broken behavior > on (slightly) malformed HTML, e.g. , > and , which > renders the function unusable on arbitrary user supplied input. I see a very co

Re: [PHP-DEV] PHP 2^3

On Monday, June 25, 2018 11:16:31 AM CDT Sara Golemon wrote: > > First, I'll admit that there's definitely some of that happening. But to > > paraphrase my daughters - "I didn't start it!". In other words - people > > are very actively looking for ways to run PHP in a Node-like manner, and > > w

Re: [PHP-DEV] PHP 8 next?

On Mon, Jun 25, 2018 at 1:16 PM Mark Baker wrote: > On 24/06/2018 18:23, Rowan Collins wrote: > > I've argued before that there should be a roadmap and a cycle for major > releases, and if not, then some agreement on what triggers one, but we've > so far not managed to agree either. > > I do beli

Re: [PHP-DEV] PHP 2^3

On Mon, Jun 25, 2018 at 7:16 PM Sara Golemon wrote: > Yeah, like I said, I must have completely missed that entire > paragraph. Mid-2020, following a late-2019 release of a "light" 7.4 > with deprecations is reasonable, though I don't think it'd be such a > bad idea if we kept it on schedule to

Re: [PHP-DEV] PHP 8 next?

On 24/06/2018 18:23, Rowan Collins wrote: I've argued before that there should be a roadmap and a cycle for major releases, and if not, then some agreement on what triggers one, but we've so far not managed to agree either. I do believe a road map and a cycle is a good idea. I'm hearing some

Re: [PHP-DEV] PHP 8 next?

On 24/06/2018 01:58, Levi Morrison wrote: Neither JIT nor FFI require backwards compatibility breaks in language. I don't think either of those particular features would substantially break the C API either. If these are the motivations for PHP 8 then I strongly object. Personally, I think that

Re: [PHP-DEV] PHP 2^3

On Mo, 2018-06-25 at 09:58 -0500, Ralph Schindler wrote: > On 6/25/18 9:13 AM, Johannes Schlüter wrote: > > > > On Mo, 2018-06-25 at 12:30 +, Zeev Suraski wrote: > > > > > > 3. Foreign Function Interface support. > > Related to this on a non-PHP-code and strategic matter I would like > > to r

Re: [PHP-DEV] PHP 2^3

On Mon, Jun 25, 2018 at 9:58 AM, Zeev Suraski wrote: > Note that I did propose that we actually have a thin depredations-only PHP > 7.4 (to give credit where credit's due, that's Dmitry's idea). This gives > us ample time without having to rush deprecations into 7.3 > I apologize. I had missed th

Re: [PHP-DEV] Re: PHP 2^3

On Mon, Jun 25, 2018 at 5:57 PM Christoph M. Becker wrote: > On 25.06.2018 at 14:30, Zeev Suraski wrote: > > > What this list is - a collection of directions around which we've > performed varying amounts of research (some of them quite a lot, like JIT), > that I think is strong grounds for us to

Re: [PHP-DEV] PHP 2^3

Thanks for taking the time to respond! On Mon, Jun 25, 2018 at 5:27 PM Sara Golemon wrote: > 1/ Pushing 8.0 as 7.3 + 1 means we're going to rush deprecations into > 7.3 which is already in fire-hose mode of last-minute, under-planned > "hey I want this toy" requests. Yes, deprecations are a lit

Re: [PHP-DEV] PHP 2^3

On 6/25/18 9:13 AM, Johannes Schlüter wrote: On Mo, 2018-06-25 at 12:30 +, Zeev Suraski wrote: 3. Foreign Function Interface support. Related to this on a non-PHP-code and strategic matter I would like to rethink PECL. Currently maintenance and installing extensions using it is a pita. Thi

[PHP-DEV] Re: PHP 2^3

On 25.06.2018 at 14:30, Zeev Suraski wrote: > What this list is - a collection of directions around which we've performed > varying amounts of research (some of them quite a lot, like JIT), that I > think is strong grounds for us to start discussing a PHP 8 timeline, and > making PHP 7.3 the la

Re: [PHP-DEV] PHP 7.1.19 - where are the gpg signatures?

On Mon, Jun 25, 2018 at 9:53 AM, Christoph M. Becker wrote: > appears to work > as well. > Yeah, because Joe and I already fixed it. :D Snooze ya lose, brother. -Sara -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe,

Re: [PHP-DEV] PHP 7.1.19 - where are the gpg signatures?

On 25.06.2018 at 16:48, Helmut K. C. Tessarek wrote: > On 2018-06-25 16:34, Sara Golemon wrote: > >> Looks like Joe accidentally generated unarmored .sig files instead of >> the usual .asc file. > > Ah, ok. .sig files are perfectly fine, too. > I just didn't see the links, nor the .sig files, sin

Re: [PHP-DEV] PHP 7.1.19 - where are the gpg signatures?

On Mon, Jun 25, 2018 at 9:48 AM, Helmut K. C. Tessarek wrote: > On 2018-06-25 16:34, Sara Golemon wrote: > Ah, ok. .sig files are perfectly fine, too. > I just didn't see the links, nor the .sig files, since no servers with > php sources seem to allow directory listing. > Yeah, we don't normally p

Re: [PHP-DEV] PHP 7.1.19 - where are the gpg signatures?

On 2018-06-25 16:34, Sara Golemon wrote: > Looks like Joe accidentally generated unarmored .sig files instead of > the usual .asc file. Ah, ok. .sig files are perfectly fine, too. I just didn't see the links, nor the .sig files, since no servers with php sources seem to allow directory listing. T

Re: [PHP-DEV] PHP 7.1.19 - where are the gpg signatures?

On Mon, Jun 25, 2018 at 6:53 AM, Helmut K. C. Tessarek wrote: > The gpg signatures for the PHP 7.1.19 source tarballs are missing. > Looks like Joe accidentally generated unarmored .sig files instead of the usual .asc file. Joe, could you re-issue the signatures as .asc files? I could probably c

Re: [PHP-DEV] PHP 2^3

On Mon, Jun 25, 2018 at 7:30 AM, Zeev Suraski wrote: > As I mentioned a few days ago I intended to send it slightly later - but as > Nikita brought up the topic of PHP 8, this is probably as good a time as any > to start the discussion. > > Please note: The goal of this email isn't to discuss i

Re: [PHP-DEV] PHP 2^3

On Mon, Jun 25, 2018 at 3:31 PM Zeev Suraski wrote: > 1. JIT. As most of you probably know, we've invested heavily in re-doing > JIT on top of the PHP 7 infrastructure. There are good news and bad news. > The good news is that - like the JIT POC we did back in 2014 - the results > for CPU inten

Re: [PHP-DEV] PHP 2^3

On Mo, 2018-06-25 at 12:30 +, Zeev Suraski wrote: > 3. Foreign Function Interface support.  Related to this on a non-PHP-code and strategic matter I would like to rethink PECL. Currently maintenance and installing extensions using it is a pita. This should be doable in a nicer way.  (i.e. pecl

Re: [PHP-DEV] PHP 8 next?

Hi Levi, On 24 June 2018 22:26:24 BST, Levi Morrison wrote: >> Are there particular breaking changes that you think would be ready >in 2 years time that wouldn't be ready in 1? > >Certainly. Large breaks require multi-year planning and multiple >releases to add migration paths, documentation and

[PHP-DEV] PHP 2^3

As I mentioned a few days ago I intended to send it slightly later - but as Nikita brought up the topic of PHP 8, this is probably as good a time as any to start the discussion. Please note: The goal of this email isn't to discuss in detail each and every topic that's mentioned, but rather to

Re: [PHP-DEV] Equality and relative ordering of objects

The part I found difficult was in the handlers - we only have `compare`, no equals. The only way we can have the handler differentiate between equality and ordering is if we pass a parameter to the handler, which means we'd have to change the header. From: `typedef int (*zend_object_compare_zvals

[PHP-DEV] PHP 7.1.19 - where are the gpg signatures?

Hello, The gpg signatures for the PHP 7.1.19 source tarballs are missing. Cheers, K. C. -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madnes

Re: [PHP-DEV] Equality and relative ordering of objects

> > Java has .equals and .compareTo; these operations are separate. In > Java neither integrates with operators. Yeah that's right. I was just pointing out that Java's == always checks against the reference and you can't override it (so it's like PHP's ===). Their .equals() method is like PHP's =

Re: [PHP-DEV] [RFC] Deprecations for PHP 7.3

On 25.06.2018 at 08:12, Stanislav Malyshev wrote: >> fgetss() function and string.strip_tags filter > > I think I disagree with "strip_tags() itself, due to its limitations and > known bugs, already has very few legitimate applications" and certainly > the manual does not have any notice to that