On Thu, Apr 28, 2022, at 9:05 AM, Côme Chilliet wrote:
> Le lundi 25 avril 2022, 18:19:33 CEST Rowan Tommins a écrit :
>> Look at how the untyped property behaves in this example:
>> https://3v4l.org/nClNs The property disappears from var_dump(), but is
>> not actually deleted from the object,
Le lundi 25 avril 2022, 18:19:33 CEST Rowan Tommins a écrit :
> Look at how the untyped property behaves in this example:
> https://3v4l.org/nClNs The property disappears from var_dump(), but is
> not actually deleted from the object, as seen by it still being private
> when assigned a new
On 21/04/2022 22:45, Mark Randall wrote:
Internals,
I have now opened voting on Undefined Property Error Promotion.
https://wiki.php.net/rfc/undefined_property_error_promotion
In case anyone missed it due to some messed-up mail headers, the thread
I intended to be a reply to this is here:
> > Are you proposing to deprecate the implicit `= null` default initializer
> > for untyped properties?
>
> Yes.
>
>
> > Thanks for the recap. For untyped properties, that's the historical
> > behavior. For typed properties, that's explained in
> >
>
On 25/04/2022 12:24, Guilliam Xavier wrote:
Hi Rowan,
(...) Also, there's this non-standard class called
"stdClass", which unlike standard classes, you can read and write any
property you like without declaring it,
Better reordered "write and read" I think. Yes, like associative arrays,
Hi Rowan,
(...) Also, there's this non-standard class called
> "stdClass", which unlike standard classes, you can read and write any
> property you like without declaring it,
Better reordered "write and read" I think. Yes, like associative arrays,
stdClass is "dynamic" by design.
> and even
On 22/04/2022 21:47, Mark Randall wrote:
The rule that anything typed must be initialized, nullable or not, is
clearish enough.
It's "clear" in the sense of "it can be described in one sentence". It's
not at all "clear" in the sense of "makes any logical sense whatsoever".
You could
On 22/04/2022 21:30, Rowan Tommins wrote:
Do you not have even a little bit of hope that we could make that less
confusing, since we're breaking everyone's old code anyway?
I seem to remember we had a discussion years ago about deleting unset on
properties, but it was being used for a very
On 22/04/2022 18:12, Mark Randall wrote:
Accessing an unset property, which currently emits a warning, will
instead throw an Error.
[...]
Re: Case 4, an untyped property without its own initializer is
effectively defaulted to null.
Imagine you're a new user, learning PHP 9.0, and learning
On 22/04/2022 14:42, Rowan Tommins wrote:
As with your previous RFC, I approve of this in principle, but am
frustrated how little time has been spent considering the edge cases, such
as the ones I mentioned here: https://externals.io/message/117487#117487
Accessing an unset property, which
On 21 April 2022 22:45:17 BST, Mark Randall wrote:
>Internals,
>
>I have now opened voting on Undefined Property Error Promotion.
>
>https://wiki.php.net/rfc/undefined_property_error_promotion
As with your previous RFC, I approve of this in principle, but am
frustrated how little time has been
Internals,
I have now opened voting on Undefined Property Error Promotion.
https://wiki.php.net/rfc/undefined_property_error_promotion
Voting ends 2022-05-05
Summary:
This RFC seeks to prevent execution continuing if the user has accessed
an undefined property without specifying that it was
12 matches
Mail list logo
