Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:75923
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.181 as permitted sender)
MIME-Version: 1.0
Sender: laruence@gmail.com
In-Reply-To: <53CF6C1A.1020208@lsces.co.uk>
References: <53CF6C1A.1020208@lsces.co.uk>
Date: Wed, 23 Jul 2014 16:12:02 +0800
Message-ID: <CABBJUpcg02DQyBtuCa+KA51OFMf9yBF90EjMz=_2meJ0T7wqEw@mail.gmail.com>
To: Lester Caine <lester@lsces.co.uk>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] phpng - loss of IS_BOOL
From: laruence@php.net (Laruence)

Hey:

On Wed, Jul 23, 2014 at 4:02 PM, Lester Caine <lester@lsces.co.uk> 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 codebase, every one of them is used simply to convert the
> bool value into some other format. Surely what would make more sense
> here is simply to make the type_flag either true or false, and retain
> the IS_BOOL as a single identifiable type? Having two types both
> indicating 'bool' just seems wrong.
there is a _IS_BOOL macro to identifiable bool type..

you can use it in your own codes.

thanks
>
> --
> Lester Caine - G8HFL
> -----------------------------
> Contact - http://lsces.co.uk/wiki/?page=contact
> L.S.Caine Electronic Services - http://lsces.co.uk
> EnquirySolve - http://enquirysolve.com/
> Model Engineers Digital Workshop - http://medw.co.uk
> Rainbow Digital Media - http://rainbowdigitalmedia.co.uk
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>



-- 
Laruence  Xinchen Hui
http://www.laruence.com/