[PHP-DEV] Feature: Null Coalescing Variable Handling Construct

Following a brief discussion on Github today about adding operators, I decided a simple-looking construct is needed and is arguably a better solution for null coalescing comparison. A common challenge: Need to test the value of a variable whose existence is unknown. Existing solutions: |$in

Re: [PHP-DEV] PHP True Async RFC - Stage 2

On Sun, Mar 16, 2025, at 10:24, Edmond Dantes wrote: > Good day, everyone. I hope you're doing well. > > https://wiki.php.net/rfc/true_async > > Here is a new version of the RFC dedicated to asynchrony. > > Key differences from the previous version: > > * The RFC is not based on Fiber; it int

Re: [PHP-DEV] PHP True Async RFC - Stage 2

On 18 March 2025 08:22:18 GMT, Edmond Dantes wrote: spawning in a scope a "second-class citizen" if `spawn foo($bar);` Reminds me of *"post-purchase rationalization"* or the *"IKEA effect".* when effort has already been invested into something, and then suddenly, there's a more convenient

Re: [PHP-DEV] Looking for a new job

On Mon, Mar 17, 2025 at 2:35 PM Dmitry Stogov wrote: > Hi, > > I have to inform, that I'm leaving Zend in two weeks. > Therefore I'm starting to think about a new job. > In case some company is interested in my competence, let's start from a > personal email communication. > > Thanks. Dmitry. >

Re: [PHP-DEV] [RFC] [Discussion] Add WHATWG compliant URL parsing API

Hi Paul, > If we want a full-featured WHATWG-URL implementation in core, would it not > be preferable (with Trevor's permission) to convert rowbot/url from > userland to core instead? Surely conversion from an existing, well-tested, > widely-used implementation would be easier/better/faster than

[PHP-DEV] Potential RFC: mb_rawurlencode() ?

Hi all, The discussion around WHATWG-URL on this list, as well as my work coordinating Uri-Interop , lead me to think PHP needs a multibyte equivalent of rawurlencode(). Broadly speaking, as far as I can tell: - For an RFC 3986 URI, delimiters need to

Re: [PHP-DEV] [RFC] [Discussion] Add WHATWG compliant URL parsing API

Hi Maté and all, There is a pre-existing userland implementation of WHATWG-URL at . Packagist reports 600K+ downloads . It is from Trevor Rowbotham, who is acknowledged in the WHATWG-URL specification itself <

Re: [PHP-DEV] PHP True Async RFC - Stage 2

On Tue, Mar 18, 2025, at 8:45 AM, Talysson Lima wrote: > If I say it's bright, you call it dark. > If I choose the east, you push for the south. > You’re not seeking a path, just a fight... > Debating with you? Not worth the time! Please do not top post. --Larry Garfield

Re: [PHP-DEV] PHP True Async RFC - Stage 2

If I say it's bright, you call it dark. If I choose the east, you push for the south. You’re not seeking a path, just a fight... Debating with you? Not worth the time! Em ter., 18 de mar. de 2025 às 03:00, Larry Garfield escreveu: > On Sun, Mar 16, 2025, at 4:24 AM, Edmond Dantes wrote: > > Good

Re: [PHP-DEV] Looking for a new job

Notified my employer, but I fear the Russia-Ukraine war prevents hiring from Russia :( @Bilge 1996: PHP is dead, learn ColdFusion 2003: PHP is dead, learn ASP.net 2006: PHP is dead, learn Ruby on Rails 2008: PHP is dead, learn Django 2012: PHP is dead, learn Flask 2013: PHP is dead, learn AngularJ

Re: [PHP-DEV] PHP True Async RFC - Stage 2

> > spawning in a scope a "second-class citizen" if `spawn foo($bar);` > Reminds me of *"post-purchase rationalization"* or the *"IKEA effect".* when effort has already been invested into something, and then suddenly, there's a more convenient way. And that convenient way seems to devalue the fi

Re: [PHP-DEV] PHP True Async RFC - Stage 2

On 18 March 2025 05:59:07 GMT, Larry Garfield wrote: >My biggest issue, though, is that I honestly can't tell what the mental model >is supposed to be. The RFC goes into detail about three different async >models. Are those standard terms you're borrowing from elsewhere, or your own >crea

Re: [PHP-DEV] PHP True Async RFC - Stage 2

Hello, Larry. > > First off, it desperately needs an "executive summary" section up at the top. > There's a *lot* going on, and having a big-picture overview would help a ton. (For > examples, see property hooks[1] and pattern matching[2].) > I looked at the examples you provided, but I still don