Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:120440
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.600.7\))
In-Reply-To: <641b1ca0-d33f-4f38-ae64-81b4abce24da@app.fastmail.com>
Date: Mon, 29 May 2023 22:28:59 +0200
Cc: php internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <51D1B70D-D77A-40A1-8AE5-534E13C67CBB@gmail.com>
References: <641b1ca0-d33f-4f38-ae64-81b4abce24da@app.fastmail.com>
To: Larry Garfield <larry@garfieldtech.com>
Subject: Re: [PHP-DEV] [RFC] Property hooks, nee accessors
From: claude.pache@gmail.com (Claude Pache)



> Le 8 mai 2023 =C3=A0 23:38, Larry Garfield <larry@garfieldtech.com> a =
=C3=A9crit :
>=20
> Ilija Tovilo and I would like to offer another RFC for your =
consideration.  It's been a while in coming, and we've evolved the =
design quite a bit just in the last week so if you saw an earlier draft =
of it in the past few months, I would encourage you to read it over =
again to make sure we're all on the same page.  I'm actually pretty =
happy with where it ended up, even if it's not the original design.  =
This approach eliminates several hard-to-implement edge cases while =
still providing a lot of functionality in one package.
>=20
> https://wiki.php.net/rfc/property-hooks
>=20

Hi,

If I understand correctly, given:

<?php

class C {

    public int $someInt;

    public float $someFloat;
   =20
    public int $someIntWithHook {
        get =3D> $field;
        set =3D> $field =3D $value;
    }

    public float $someFloatWithHook {
        get =3D> $field;
        set =3D> $field =3D $value;
    }

}
?>

we have:

<?php
$obj =3D new C;
var_dump($obj->someInt =3D 42.0); // int(42)
var_dump($obj->someFloat =3D 42); // float(42)
?>

but:

<?php
$obj =3D new C;
var_dump($obj->someIntWithHook =3D 42.0); // float(42)
var_dump($obj->someFloatWithHook =3D 42); // int(42)
?>

If I am correct, it means that the =E2=80=9CThis also implies that =
adding a set hook to a property cannot change the result of the =3D =
operator=E2=80=9D statement is a bit too optimistic.


=E2=80=94Claude