Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:93422
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.181 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <573ED827.7030007@lsces.co.uk>
References: <CAL=_i_mcJoFnPgeU5FQCJN=SDYnNK7Jz8zoVMv9EMuWaGRYSMg@mail.gmail.com>
 <573ED827.7030007@lsces.co.uk>
Date: Fri, 20 May 2016 11:47:12 -0400
Message-ID: <CAFp73Xv9o9Bh96wY1uWYnbzVpRAnTz4+nfgatuCOTL3N8edPvw@mail.gmail.com>
To: Lester Caine <lester@lsces.co.uk>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a1144805437e82605334802de
Subject: Re: [PHP-DEV] [RFC][Vote] Typed Properties
From: guilhermeblanco@gmail.com ("guilhermeblanco@gmail.com")

--001a1144805437e82605334802de
Content-Type: text/plain; charset=UTF-8

Joe, I fixed a minor typo in the RFC, hope you didn't mind. =)

On Fri, May 20, 2016 at 5:25 AM, Lester Caine <lester@lsces.co.uk> wrote:

> 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 [<array_dim>] 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
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>


-- 
Guilherme Blanco
Lead Architect at E-Block

--001a1144805437e82605334802de--