Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:91770 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 11534 invoked from network); 19 Mar 2016 10:54:07 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 19 Mar 2016 10:54:07 -0000 Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.214 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 217.147.176.214 mail4-2.serversure.net Linux 2.6 Received: from [217.147.176.214] ([217.147.176.214:33672] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 4A/16-03097-ECF2DE65 for ; Sat, 19 Mar 2016 05:54:07 -0500 Received: (qmail 27278 invoked by uid 89); 19 Mar 2016 10:54:03 -0000 Received: by simscan 1.3.1 ppid: 27272, pid: 27275, t: 0.0579s scanners: attach: 1.3.1 clamav: 0.96/m:52/d:10677 Received: from unknown (HELO ?10.0.0.7?) (lester@rainbowdigitalmedia.org.uk@81.155.186.161) by mail4.serversure.net with ESMTPA; 19 Mar 2016 10:54:03 -0000 To: internals@lists.php.net References: <56EC69EF.1090003@fleshgrinder.com> <56ECCFCB.6090105@garfieldtech.com> <56ED28BD.4040900@fleshgrinder.com> Message-ID: <56ED2FCB.6030609@lsces.co.uk> Date: Sat, 19 Mar 2016 10:54:03 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <56ED28BD.4040900@fleshgrinder.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC Discussion] Typed Properties From: lester@lsces.co.uk (Lester Caine) On 19/03/16 10:23, Fleshgrinder wrote: > Properties need the ability to be void even after construction and it is > up to the object to keep track and ensure state. Nullability is imho not > necessary at all. So we are all in line here. If the record I am working with identifies elements are incorrectly matched, then making a value 'void' is the correct action. We would just NULL that identifier and fire off a delete to the linked record in the database. Otherwise we have to create additional logic to handle that. -- 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