Re: Type hinting
| From: | Thomas Nunninger | Date: | Thu, 27 May 2010 08:09:30 +0000 |
| Subject: | Re: Type hinting | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-48489@lists.php.net to get a copy of this message | ||
Hi,
if it comes to auto-converting (that's different from existing type-juggling):
wouldn't it be nice, to change type-juggling as well?
I know about BC breaks here, thus it would need till PHP 7 or so to become the
default behavior. But I think, BC breaks mainly occur in the cases where
type-juggling is more hiding programming errors than helping the user - that
is: where the developer should really care about checking and/or casting.
As an advantage, hints and type-juggling would at least behave consistent,
reducing complexity for the users (and perhaps internally for you as core
developers as well).
Am Donnerstag, 27. Mai 2010 07:42:32 schrieb Zeev Suraski:
> Can anybody share with us *common* cases where strict typing would be
> necessary, and the proposed auto-converting type hints won't do?
If you use CouchDB as backend (where data is stored as JSON), there is a
difference if you store "42" , 42, or 42.0. IIRC I read on the CouchDB
mailing list that this can influence view sorting. (As I strictly care about
types in my application, I didn't had problems yet.)
Thomas