Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:102343
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.173 as permitted sender)
MIME-Version: 1.0
Sender: nicolas.grekas@gmail.com
In-Reply-To: <CAF+90c_L7S+EB8YxdNNpNZ7NhhYwCbwEw5_TSnSwUNN-zLVvCg@mail.gmail.com>
References: <CAF+90c_L7S+EB8YxdNNpNZ7NhhYwCbwEw5_TSnSwUNN-zLVvCg@mail.gmail.com>
Date: Thu, 21 Jun 2018 16:08:09 +0200
Message-ID: <CAOWwgpkJyceDjKoSZ+PDcCjvUvgp=FeDV9aWE2m2jjtVuhP1Tw@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000002980b5056f2773dc"
Subject: Re: [PHP-DEV] [RFC] Typed Properties
From: nicolas.grekas+php@gmail.com (Nicolas Grekas)

--0000000000002980b5056f2773dc
Content-Type: text/plain; charset="UTF-8"

Hi Nikita, Bob,

    https://wiki.php.net/rfc/typed_properties_v2
>

This is really well thought and written, sounds really primising.
I agree that "References without intrinsic type" look the best.

I anticipate one case on Symfony VarDumper that will break on typed
references:

the only way to detect references is by injecting cookies in arrays, e.g.:
$a = (array) $someObjectOrArray;
$cookie = new stdClass();
$b = $a;
$b[$k] = $cookie;
if ($a[$k] === $cookie) {
  // Here we have a reference
}

I'd need to wrap the assignation in a try/catch now:
try {
    $b[$k] = $cookie;
} catch (TypeError $e) {
  // Here we have a typed reference that doesn't accept stdclass
}

So far so good I suppose. I just wanted to raise the point if it matters at
all.

Thank you,
Nicolas

--0000000000002980b5056f2773dc--