Re: [PHP-DEV] [RFC] [Discussion] nameof

On Sat, May 13, 2023, at 7:27 AM, Robert Landers wrote: > Hello Internals, > > It is with much trepidation and excitement that I'd like to announce > the `nameof` RFC (https://wiki.php.net/rfc/nameof). It has changed > quite a bit in the last couple of days, so if you haven't seen the > latest draf

Re: [PHP-DEV] [RFC] [Discussion] Deprecate functions with overloaded signatures

On Tue, May 16, 2023, at 2:26 PM, Derick Rethans wrote: > On 15 May 2023 13:38:56 GMT-05:00, Larry Garfield > wrote: >>On Mon, May 15, 2023, at 6:36 PM, Rowan Tommins wrote: >>> On 15 May 2023 09:54:41 BST, "G. P. B." wrote: >>> Why are we assuming that PHP 9.0 is going to come after PHP 8.4

Re: [PHP-DEV] [RFC] Define proper semantics for range() function

On Tue, 16 May 2023 at 17:49, Jorg Sowa wrote: > Thank you. That makes sense. I have last question about case with integer > and string digit, i.e. range('5', 10) or range('1', 9). What would be in > this case expected output? I couldn't find any test cases covering this > example. > I've added

Re: [PHP-DEV] [RFC] [Discussion] nameof

Op ma 15 mei 2023 om 20:06 schreef Rowan Tommins : > > On 15 May 2023 14:07:31 BST, Lydia de Jongh wrote: > >> ... > >> #[SomeAttribute(callback: nameof(\Acme\bar(...))] > >> ... > > > >This callback to nameof(). is really terrible 😣😣 > > Just to be clear, the "callback:" in that example is e

Re: [PHP-DEV] [RFC] Define proper semantics for range() function

Thank you. That makes sense. I have last question about case with integer and string digit, i.e. range('5', 10) or range('1', 9). What would be in this case expected output? I couldn't find any test cases covering this example. Kind regards, Jorg On Tue, May 16, 2023 at 2:29 PM G. P. B. wrote:

Re: [PHP-DEV] RFC [Discussion]: Marking overridden methods (#[\Override])

On Thu, 11 May 2023 at 17:37, Tim Düsterhus wrote: > > Hi > > I'm now opening discussion for the RFC "Marking overridden methods > (#[\Override])": > > I'm now opening discussion for the RFC "Marking overridden methods > (#[\Override])": This RFC is probably a good idea, even if the number of pe

Re: [PHP-DEV] Planning ahead, will 8.5 exist and major version decisions (was: Deprecate functions with overloaded signatures)

> [2] I am sure lots of userland people and other people will have >opinions also. I just don't think they will be as insightful or useful >in this conversation. Userland here and I agree with you completely. My opinion is that the maintainers should decide, since they bear the burden of the deci

Re: [PHP-DEV] [RFC] [Discussion] Deprecate functions with overloaded signatures

On 15 May 2023 13:38:56 GMT-05:00, Larry Garfield wrote: >On Mon, May 15, 2023, at 6:36 PM, Rowan Tommins wrote: >> On 15 May 2023 09:54:41 BST, "G. P. B." wrote: >> >>>Why are we assuming that PHP 9.0 is going to come after PHP 8.4? >> >> Historically, PHP has had a major release roughly every

Re: [PHP-DEV] Planning ahead, will 8.5 exist and major version decisions (was: Deprecate functions with overloaded signatures)

On Tue, 16 May 2023 at 13:39, Dan Ackroyd wrote: > > * Are there any things being worked on that would deserve or require a > major version bump in PHP? > I think there are two conflicting ideas of what a major version should be: a) A major version is an ad hoc event that happens when somethin

[PHP-DEV] Planning ahead, will 8.5 exist and major version decisions (was: Deprecate functions with overloaded signatures)

On Sat, 13 May 2023 at 00:08, Larry Garfield wrote: > > I am actually tempted to propose that we do deprecations at the very > start of a release, 9.0 and 9.1 only, and then not allow them for the > rest of that major, for that exact reason. That sounds really unwise. People aren't that enthusia

Re: [PHP-DEV] [RFC] [Discussion] Deprecate functions with overloaded signatures

On Sat, 13 May 2023 at 00:08, Larry Garfield wrote: > > That means it's impossible to write code that works from 8.2 to 9.0 without > version checks. The overlap period is only 2 releases (8.3 and 8.4). That's > too short of a window. That it is too short, is an opinion. Having one version w

Re: [PHP-DEV] [RFC] Define proper semantics for range() function

On Mon, 15 May 2023 at 23:53, Jorg Sowa wrote: > Hello! > > I have one concern about the part: > > > Emit an E_WARNING when $start or $end is cast to an integer because the > other boundary input is a number or numeric string. (e.g. range > ('5', 'z'); or range

Re: [PHP-DEV] [RFC] [Discussion] Deprecate functions with overloaded signatures

On Tue, 16 May 2023 at 12:03, G. P. B. wrote: > > Because this proposal of "let's do majors every 5 years" now reduces what > we can do, as we cannot (or should not) deprecate stuff in X.0, as it makes > it harder for people to upgrade to the new major (see how we postponed the > 8.0 deprecation

Re: [PHP-DEV] [RFC] [Discussion] Deprecate functions with overloaded signatures

On Mon, 15 May 2023 at 19:39, Larry Garfield wrote: > Tangent: If I were to put together an RFC that set out such a 5 year cycle > expectation with reasonable guidelines around when things could be > deprecated, would anyone actually support it? > No, as this doesn't solve the problem. Best reg

Re: [PHP-DEV] [RFC] [Discussion] Deprecate functions with overloaded signatures

On Mon, 15 May 2023 at 19:36, Rowan Tommins wrote: > On 15 May 2023 09:54:41 BST, "G. P. B." wrote: > > >Why are we assuming that PHP 9.0 is going to come after PHP 8.4? > > Historically, PHP has had a major release roughly every five years. The > main exception is PHP 6, which was never release