Re: Fix ReflectionType::__toString() BC break
| From: | Johannes Schlüter | Date: | Wed, 21 Sep 2016 09:56:54 +0000 |
| Subject: | Re: Fix ReflectionType::__toString() BC break | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-96046@lists.php.net to get a copy of this message | ||
Hi,
On Wed, 2016-09-21 at 10:55 +0200, Nicolas Grekas wrote:
> our turn to be hit by this 7.1 BC break in Symfony:
>
Attachment: [application/pgp-signature] This is a digitally signed message part signature.asc
ReflectionType::__toString() now adds a
> ? in front of type hints where
> null is allowed by their default values.
Curious: Why do you depend on the string representation? What
information is not available in a proper interface?
I won't like to call a toString() representation a committed interface.
johannes
Attachment: [application/pgp-signature] This is a digitally signed message part signature.asc