Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:88370
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
Message-ID: <55FD2F61.9010603@lsces.co.uk>
Date: Sat, 19 Sep 2015 10:48:17 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.1.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Coding styles ...
From: lester@lsces.co.uk (Lester Caine)

I get that a lot of people think that the only way forward with PHP is
fully typed, strict checking and blocking anything that may be deemed to
be risky. However PHP7 has not yet dropped the simple object-less style
of programming that it originally developed from. That is why tidying up
a simple procedural style of working still has a place. The debate on
'exists()' or to give it a tidier title 'variable_exists()' is more
about just how much of a procedural style of programming remains in PHP
in the future. Yes there are other ways of working, and using
associative arrays direct gives a different set of tools, which then
morph again in objects, and it's the piecemeal way things have been
bolted on which has caused that so that the 'simple' functions have
fallen through the gaps?

array::exists() and object::exists() would have been tidy extensions to
exists() if one was starting again with a clean sheet, but we have what
we have and procedural PHP is still integral so can we please just clean
up the gaps rather than pushing 'more modern' ways of working.

-- 
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