Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:93559
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.214 cause and error)
To: internals@lists.php.net
References: <CAL=_i_mcJoFnPgeU5FQCJN=SDYnNK7Jz8zoVMv9EMuWaGRYSMg@mail.gmail.com>
 <CAL=_i_=EqNoHvXmY+RdQW-reC4YF8AkuWFtGGJGOOSqX4a010g@mail.gmail.com>
 <cfe8404a-54f6-24b7-0ba8-8f807c820821@zend.com>
 <CAL=_i_kze8MNSmpg4WT+EJCRPmvty=8DA6DkuHSx+WCBzJjytg@mail.gmail.com>
 <CAF+90c9cBqKfy_q5rME1u56Rq366niYUBDTY+3_2iFJSZD9fDA@mail.gmail.com>
 <CANUQDCj0O6aVwTqo+CcAbX8AWvwPQHfhRtsYRUrMS_aFjHM5RQ@mail.gmail.com>
 <7B.12.14311.F79C5475@pb1.pair.com>
 <1b12b09f-f190-dca0-51d9-468e9c571268@fleshgrinder.com>
 <4ec823c6-b039-fc91-7c78-60d67719cd81@gmail.com>
 <00482771-3a07-06cf-ee8d-cd83a301c7e7@fleshgrinder.com>
 <a65f2a52-f2fd-2a08-966d-2f2c30badfbd@gmail.com>
 <1ac579b7-6bf3-f362-c045-0261abcfa17c@fleshgrinder.com>
 <f6ea7f29-e693-e616-a588-c88b46c0b1a1@gmail.com>
 <2f058fee-f230-739f-4ed5-ff7d0cabe924@fleshgrinder.com>
 <7c3f6b51-f93b-c69f-a592-7bb0a00586e6@gmail.com>
 <528dd5dc-0e17-d766-a83f-02e2429277fa@fleshgrinder.com>
Message-ID: <5746E0D7.6020806@lsces.co.uk>
Date: Thu, 26 May 2016 12:41:11 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.7.0
MIME-Version: 1.0
In-Reply-To: <528dd5dc-0e17-d766-a83f-02e2429277fa@fleshgrinder.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC][Vote] Typed Properties
From: lester@lsces.co.uk (Lester Caine)

Bare with me ... just trying to fill in a few of the gaps in the current
documentation.

On 26/05/16 11:49, Fleshgrinder wrote:
>   $g = new class { public $x; };
> 
>   var_dump(isset($g->x));              // false

isset manual entry does not say what happens if $g->x does not exist but
the false here could equally be 'does not exist' if unset has been
called somewhere?

>   var_dump(property_exists($g, 'x'));  // true

or array_key_exists('x', $g) in our consistent style but as has been
pointed out we do not have a simple 'exists' ...
$g->exists('x') ?
along with $g->isinit('x')

>   var_dump($g->x);                     // null + E_NOTICE Uninitialized
>   var_dump(is_null($g->x));            // true + E_NOTICE Uninitialized
>   var_dump($g->x == null);             // true + E_NOTICE Uninitialized
>   var_dump($g->x === null);            // true + E_NOTICE Uninitialized

Unless null IS the required initial value? Why should we have to
initialize a nullable typed property explicitly?

I'm still stuck in the simple model of things where 'x' is expandable so
we have the simple generic variable of old (PHP4 days) which now has
additional attributes such as accessibility (public etc) and a few
special cases of type filtering but is lacking a tidy way of adding the
more useful filtering attributes such as constraints and yes typing.

properties and associative arrays are simply managed list of these
simple variables so why do we need different functions to access them.
Within a class isset($x) should mirror isset($this->x) and exists($x)
makes sense along with other 'object' related functions, but is there no
way to get back to a lot simpler consistent handling of variables ...
and a more constructive way to add flexible type constraints.

-- 
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