Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:93412 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 65902 invoked from network); 20 May 2016 09:26:05 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 May 2016 09:26:05 -0000 Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; 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:47931] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 41/A9-05406-B28DE375 for ; Fri, 20 May 2016 05:26:03 -0400 Received: (qmail 4199 invoked by uid 89); 20 May 2016 09:26:00 -0000 Received: by simscan 1.3.1 ppid: 4193, pid: 4196, t: 0.1353s 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.138.11.136) by mail4.serversure.net with ESMTPA; 20 May 2016 09:26:00 -0000 To: internals@lists.php.net References: Message-ID: <573ED827.7030007@lsces.co.uk> Date: Fri, 20 May 2016 10:25:59 +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: 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) On 20/05/16 07:05, Joe Watkins wrote: > Morning internals, > > Since we have our answer on nullable types, typed properties can now go > to vote. > > https://wiki.php.net/rfc/typed-properties#vote > > Note that, support for nullability as RFC'd will be merged when the > implementation for nullable_types is merged into master. I have just realised exactly why I have a problem with most of this ... Domain! Used as an 'OtherThing' This is ALSO attributes, since an SQL domain defines all of the attributes that I need to handle in relation to variables. 'int' on it's own does very little since one still needs to add all the other checks, but adding 'types' as a properly formatted domain solves all the problems I'm looking at ... and leaves plenty of room for others to abuse the in their own way? http://www.firebirdsql.org/file/documentation/reference_manuals/fblangref25-en/html/fblangref25-ddl-domn.html Note such elements as [] to allow for arrays of a datatype although that still leaves the handling of mix arrays. Some of the conditions may seem irreverent, but if the domain is a set of keys for an array that logic then makes sense? I can even see the addition of a 'read only' flag to solve that problem while still constraining the initial setting of a domain. But this is simply user land code and does not need a small subset of elements of it added to the code base? -- 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