Re: [RFC][Vote] Typed Properties

From: Date: Thu, 26 May 2016 22:03:38 +0000
Subject: Re: [RFC][Vote] Typed Properties
References: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15  Groups: php.internals 
Request: Send a blank email to internals+get-93593@lists.php.net to get a copy of this message
On 26/05/16 22:38, Rowan Collins wrote: >>> // accessing $me->marriage or $me->death returns NULL (because they >>> >allow nulls) but raises E_NOTICE >> BUT DateTime currently will not store 'null' - it returns 'now' >> instead. >> We end up having to store string or integer values because we can't >> store a null date :( > > That's exactly what ?DateTime is for - "either DateTime or Null", just > like in a database. > > In most type systems, there is no such thing as "a null date" - if it's > null, it's not a date, it's a null value. The exact question here then is in relation to just how one uses 'DateTime' in this situation? Or more accurately how one maintains the 'or Null' state when the type does not allow null itself? -- 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

« previous php.internals (#93593) next »