RE: [PHP-DEV] Scalar type hints and scalar type name aliases causeconfuson
| From: | Anatol Belski | Date: | Wed, 14 Oct 2015 09:57:32 +0000 |
| Subject: | RE: [PHP-DEV] Scalar type hints and scalar type name aliases causeconfuson | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-88789@lists.php.net to get a copy of this message | ||
Hi Andrea,
> -----Original Message-----
> From: Andrea Faulds [mailto:ajf@ajf.me]
> Sent: Wednesday, October 14, 2015 12:53 AM
> To: internals@lists.php.net
> Subject: Re: [PHP-DEV] Scalar type hints and scalar type name aliases
> causeconfuson
>
> Hi Dmitry,
>
> Dmitry Stogov wrote:
> >
> > I also don't like reserving new class names or limiting their use.
> > The message above looks clear and it shouldn't be a big problem to
> > implement the fix.
> > This fix shouldn't change anything except error message, so it'll make
> > minimal risk for 7.0 release process.
> >
>
> Just changing error messages would work, but it's an unclean solution.
> It would be changing existing naming conventions ('integer' in English,
> 'int' in
> code). Still, it's better than nothing if we can't reserve the names.
>
People already ported a lot of stuff to 7.0, or get already trained, etc. So changing the error
message looks like the only how far we can go at current stage. It is clear enough to express the
necessary error, and it is soft enough to will possibly break some unit tests but not the actual
codes.
Thanks
Anatol