On 23 Jul 2014, at 09:49, Lester Caine wrote:
> I'm looking for the explanation as to why it HAS to change rather than
> anything else. I can see that using the 64bit value field is overkill,
> but there is still plenty of spare space in the TYPE element to not have
> to create an extra object t
On 23/07/14 09:12, Laruence wrote:
> On Wed, Jul 23, 2014 at 4:02 PM, Lester Caine wrote:
>> > I'm trying to work through some of the more subtle changes in phpng and
>> > one that sticks out is the loss of IS_BOOL. I think the explanation is
>> > that it removes a read, but while I'm only seeing
Hey:
On Wed, Jul 23, 2014 at 4:02 PM, Lester Caine wrote:
> I'm trying to work through some of the more subtle changes in phpng and
> one that sticks out is the loss of IS_BOOL. I think the explanation is
> that it removes a read, but while I'm only seeing a few uses of is_bool
> across the codeb
I'm trying to work through some of the more subtle changes in phpng and
one that sticks out is the loss of IS_BOOL. I think the explanation is
that it removes a read, but while I'm only seeing a few uses of is_bool
across the codebase, every one of them is used simply to convert the
bool value into
