On 18/09/15 19:38, Rowan Collins wrote: > The examples Lester and Robert have come up with make sense in > themselves, but are not architectures I would choose precisely because > they are opaque (you have to remember what unset() and null mean) and > hard to extend (there's no way to introduce a 4th state alongside the > unset/null/value triad).
There are many 'essential' features of PHP that I'm unlikely to use before I die. The coding style I use works for me and I'm blowed if I will install composer on any system. My way of working takes advantage of the fact that we DON'T have to sit down and define and type every single variable used. In fact forcing me to type variables actually breaks my code because I'm just as likely to pass an array of data for a new record as an integer to access an existing one. We are not worried about how YOU use PHP, but how many other people use it ... The problem with isset is not one that affects me directly as I do use a different style and only see 'expand' in libraries, but I've seen it often enough via third party libraries to know that it needs fixing and that has nothing to do with this mythical '4th state', just the current state which we can't detect without notices. -- 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
