Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:67598
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.45 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <6dae6c81-3e50-42f3-9a7e-87eedf8861d4@email.android.com>
References: <CAAyV7nG126YkpOF-EShHbf=4rgX7gQ2VE0ShRh0-50_Yr--h4g@mail.gmail.com>
	<6dae6c81-3e50-42f3-9a7e-87eedf8861d4@email.android.com>
Date: Fri, 31 May 2013 16:03:34 -0400
Message-ID: <CAAyV7nEOvvuLnrz0bO=gvb6zJWms+X9EcbR_77Op00W5s=MHeA@mail.gmail.com>
To: Derick Rethans <derick@php.net>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c2e2581b573e04de091ca6
Subject: Re: [PHP-DEV] 5.NEXT Integer and String type modifications
From: ircmaxell@gmail.com (Anthony Ferrara)

--001a11c2e2581b573e04de091ca6
Content-Type: text/plain; charset=ISO-8859-1

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

--001a11c2e2581b573e04de091ca6--