Re: [PHP-DEV] Request for opinions: bug vs feature - change intokenization of yield from

2024-07-20 Thread Marco Aurélio Deleu
> On 20 Jul 2024, at 11:30, Tim Düsterhus wrote: > > Hi > >> On 7/19/24 00:51, Christoph M. Becker wrote: >> And frankly, how much code would be affected? I mean, does anybody >> actually put a comment between `yield` and `from`? Is there a case >> where this may make sense? "Because we

Re: [PHP-DEV] Request for opinions: bug vs feature - change in tokenization of yield from

2024-07-18 Thread Marco Aurélio Deleu
be supported. If a Ubuntu LTS user gets an error, pointing out that they're relying on an accidental behavior only present in 9 patch releases of the entire PHP lifecycle seems good enough. > On 18 Jul 2024, at 16:05, Tim Düsterhus wrote: > > Hi > >> On 7/18/24 19:48, Marco A

Re: [PHP-DEV] Request for opinions: bug vs feature - change in tokenization of yield from

2024-07-18 Thread Marco Aurélio Deleu
> On 17 Jul 2024, at 20:16, Juliette Reinders Folmer > wrote: > >  Hi all, > > I recently discovered a change was made to the Tokenizer in PHP 8.3.0 which > now allows for a comment to exist between the `yield` and `from` keyword from > the `yield from` keyword. > Before PHP 8.3, this was

Re: [PHP-DEV] Static class

2024-06-16 Thread Marco Aurélio Deleu
Marco Deleu > >> You may have core developers that voted no due to maintenance burden, but if >> said maintainer is no longer active and new maintainers don't mind it, it's >> a moot argument because people changed. > > The maintenance burden argument is actually a good example of *not*

Re: [PHP-DEV] Static class

2024-06-15 Thread Marco Aurélio Deleu
> On 15 Jun 2024, at 14:11, Rowan Tommins [IMSoP] wrote: > > I fundamentally disagree with this assertion. > > If somebody makes a valid point, it doesn't automatically become invalid > because time has passed, or because nobody happens to repeat it in a later > e-mail thread. > > If I

Re: [PHP-DEV] Proposal: AS assertions

2024-03-19 Thread Marco Aurélio Deleu
Marco Deleu > On 19 Mar 2024, at 14:51, Ilija Tovilo wrote: > > Hi Robert > >> On Tue, Mar 19, 2024 at 5:24 PM Robert Landers >> wrote: >> >> I've been thinking about this as an RFC for awhile, but with generics >> being far off (if at all), I'd like to propose a useful idea: reusing >>

Re: [PHP-DEV] [RFC][Under discussion] RFC1867 for non-POST HTTP verbs

2023-10-06 Thread Marco Aurélio Deleu
Marco Deleu > On 6 Oct 2023, at 19:39, Ben Ramsey wrote: > > On 10/6/23 11:18, Jakub Zelenka wrote: >> Hi, >>> On Fri, Oct 6, 2023 at 2:44 PM Ilija Tovilo wrote: >>> https://wiki.php.net/rfc/rfc1867-non-post >>> >>> >> It should probably explicitly mention that it uses the same inis

Re: PSR-11 and the next steps - Service Provider Interop

2020-01-09 Thread Marco Aurélio Deleu
I would be interested in a Service Provider PSR inline with PSR 11. I remember discussing this with Napoli at the last PHP Serbia conference and it was something he thought about pursuing as well. On Wednesday, January 8, 2020 at 8:37:34 PM UTC+1, Benjamin Mack wrote: > > Hi list, > > since we

Configuration Standard

2019-06-06 Thread Marco Aurélio Deleu
Hi everyone, I was wondering if there ever was or if there is interest in defining a standard for configurations / settings that would mostly benefit package developers. A few months ago Laravel 5.8 broke a lot of packages by changing how .env files are handled, which led to this really good

Re: Secretary Elections - Nominations Needed!

2018-08-04 Thread Marco Aurélio Deleu
Hi again, sorry for the late reply. I actually have been visiting this thread since the Twitter account tweeted about this for the first time. Seeing that nobody was getting involved,I felt like I could be of some help. But now that others (probably more prepared for the position) have showed

[vagrant-up] Machine constantly hanging at start up or halt

2016-09-09 Thread Marco Aurélio Deleu
I have a machine built by puphpet (with cent os) that usually hangs on *local: Warning: Remote connection disconnect. Retrying...* and I have to CTRL + C from it, run *vagrant halt *and then run *vagrant up* again. This usually happens 3 to 5 times on a daily basis (everytime I need to turn the