Re: 5.NEXT Integer and String type modifications
| From: | Anthony Ferrara | Date: | Fri, 31 May 2013 20:03:34 +0000 |
| Subject: | Re: 5.NEXT Integer and String type modifications | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-67598@lists.php.net to get a copy of this message | ||
Derick,
In principle I think this is great thing to do. Not having a 64 bit type is
> annoying. I'm a bit curious on how this is going to work with all sorts of
> object wrappers that are now in place as workaround. And casting int64 to
> int32 needs to very well looked at as well.
>
>
As far as the casting, my first reaction would be to raise an
E_ENGINE_NOTICE on data loss (casting from int64 to int32 with ints > 32
bit) and then adjusting the value to the nearest representable value
(LONG_MAX or LONG_MIN). In other words, it may need to be more than a
simple cast (an inline function perhaps)...
As far as object wrappers, any particular examples that you're thinking of?
Thanks for the thoughts
Anthony