On 23 November 2023 01:37:06 GMT, Claude Pache wrote:
>What you describe in the last sentence is what was initially designed and
>implemented by the RFC: https://wiki.php.net/rfc/typed_properties_v2 (section
>Overloaded Properties).
>
>However, it was later changed to the current semantics (unse
On Thu, Nov 23, 2023 at 7:00 AM Stephen Reay wrote:
>
>
>
> > On 21 Nov 2023, at 06:48, Mike Schinkel wrote:
> >
> > Wow.
> >
>
> Hi,
>
> (This is not a direct reply to Mike, his just seems to be less shouty than
> other recent emails)
>
> I'm not *particularly* bothered by the results of this s
> On 21 Nov 2023, at 06:48, Mike Schinkel wrote:
>
> Wow.
>
Hi,
(This is not a direct reply to Mike, his just seems to be less shouty than
other recent emails)
I'm not *particularly* bothered by the results of this specific RFC either way
- a *similar enough* result is already possible
On 11/21/23 20:17, Ben Ramsey wrote:
On Nov 21, 2023, at 18:22, G. P. B. wrote:
On Tue, 21 Nov 2023 at 21:10, Ben Ramsey mailto:ram...@php.net>> wrote:
We’ve discussed this among release managers, and I’m updating this
thread to clarify that I was mistaken about what the dates for supported
ve
> Le 22 nov. 2023 à 23:17, Rowan Tommins a écrit :
>
> I'm probably going to regret asking this, but is there some reason it works
> that way? Is there any chance of changing it to just:
>
>> Typed properties start off as uninitialized.
>>
>> Once you've assigned a value, you can't go back t
On 22 November 2023 14:12:09 GMT, Nicolas Grekas
wrote:
>I think there is an inaccuracy that needs to be fixed in the after-unset
>state : as noted later in the RFC, magic accessors are called after an
>unset($this->typedProps). This means the state cannot be described as
>identical ("uninitializ
On Wed, Nov 22, 2023 at 2:08 PM G. P. B. wrote:
> On Wed, 22 Nov 2023 at 07:36, Mike Schinkel wrote:
>
> > On Nov 21, 2023 at 11:33 PM, >
> wrote:
> >
> > What is the point of a major release if we cannot even do such a BC
> break?
> > We don't even know when PHP 9.0 is going to happen yet.
> >
On Wed, Nov 22, 2023 at 10:06 PM Deleu wrote:
>
> Hi!
>
> Earlier today I was working on a small tool to invalidate PHP Sessions in a
> legacy system. I quickly found out about the `session_decode()` function,
> but unfortunately this function requires an active session and it is
> completely stat
Hi!
Earlier today I was working on a small tool to invalidate PHP Sessions in a
legacy system. I quickly found out about the `session_decode()` function,
but unfortunately this function requires an active session and it is
completely stateful, which means when I try to decode a specific session
da
Hi all,
Ilija and I would like to start a discussion about the following RFC:
> https://wiki.php.net/rfc/pass_scope_to_magic_accessors
>
> When using magic methods to access actual properties, respecting their
> declared visibility is often desired. Yet, accessing the calling scope to
> emulate th
> More importantly, it is possible to write cross compatible code, even
> without changing anything about is_resource(), if we convert streams to
> opaque objects.
> It might be tedious and one might need to have redundant instanceof checks
> with is_resource() if one does not want to check for a f
On Wed, 22 Nov 2023 at 07:36, Mike Schinkel wrote:
> On Nov 21, 2023 at 11:33 PM, > wrote:
>
> What is the point of a major release if we cannot even do such a BC break?
> We don't even know when PHP 9.0 is going to happen yet.
>
>
> I have been using Go for about four years now and it seems they
> Le 21 nov. 2023 à 00:08, Rowan Tommins a écrit :
>
> I've revised the RFC; it now proposes to keep the implicit "= null" for
> untyped properties, although I'm still interested in suggestions for other
> strategies around that.
Hi,
If you really want untyped property not being implicitl
Hi Rowan, Larry,
Thanks for the RFC.
I think there is an inaccuracy that needs to be fixed in the after-unset
state : as noted later in the RFC, magic accessors are called after an
unset($this->typedProps). This means the state cannot be described as
identical ("uninitialized') before and after u
On Tue, Nov 21, 2023 at 12:41 AM Larry Garfield wrote:
>
> On Mon, Nov 20, 2023, at 11:08 PM, Rowan Tommins wrote:
> > On 16/11/2023 20:41, Rowan Tommins wrote:
> >> Hi all,
> >>
> >> I have finally written up an RFC I have been considering for some
> >> time: Harmonise "untyped" and "typed" prope
Am 20.11.2023 um 22:00 schrieb Lanre Waju :
> I will have to disagree with everything you said:
Side-note: This is IMHO not a good intro into a discussion ;-)
> I outlined what a static class would be: A class that cannot be instantiated
> in which all members are implicitly static. We already h
16 matches
Mail list logo
