Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:92952
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.174 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <572390DC.1020108@lsces.co.uk>
References: <BY2PR0201MB178479B3AF8BD49583233034BF6E0@BY2PR0201MB1784.namprd02.prod.outlook.com>
	<CADqTB_hH4=Rx2ZV_WSJuCPzbnA-ERyFUE8ZsCew2Z6p0+FHWsg@mail.gmail.com>
	<5720A6B4.4000307@lsces.co.uk>
	<CADyq6sKBV0n+xnVhRxsP5RDf0oRLMnNO-BM1VEudRgcK1s199A@mail.gmail.com>
	<CADyq6s+P5p-xdJ8CQaFo3Nrwe7ooyCLg1p=98E0kcSscBbSe8A@mail.gmail.com>
	<CADyq6sJp-krEpGgat7hWm2YpvtfwAfK1ya0as4Tv2qtCSeNgAw@mail.gmail.com>
	<5721B9DD.3050300@lsces.co.uk>
	<CADyq6s+nJoHkMmA+iupA0+7jwJskkdLTe=os=gZDt3dqaJxT7A@mail.gmail.com>
	<57231ADD.9040006@lsces.co.uk>
	<CADyq6s+uELdzWoMd0GBvby205Po_xEpxKoEBkSc_qbxsS3YeXQ@mail.gmail.com>
	<572326A3.7000809@lsces.co.uk>
	<cb7724e7-7436-3013-5a3a-f7df6c35ed86@gmail.com>
	<57234D3D.1070602@lsces.co.uk>
	<79c9df57-ee45-f415-3172-95f8229bbece@gmail.com>
	<CAEPJdunLsPfnE5ebZkcARRO_RR9ni1jWQJg_FW_9XZm9XhpPsQ@mail.gmail.com>
	<57235F20.5080707@lsces.co.uk>
	<43b9c67f-3ec7-bacc-2608-552abbd1a3fa@gmail.com>
	<57237B36.1070301@lsces.co.uk>
	<0d71618b-2ffa-7273-f9b9-aeabc35f4211@gmail.com>
	<572390DC.1020108@lsces.co.uk>
Date: Fri, 29 Apr 2016 10:57:08 -0600
Message-ID: <CAObuZdvpjhMqjp47ds1zJ8=wxwDXwQ=qRxS=vJ3Rgkj4U7L5bg@mail.gmail.com>
To: Lester Caine <lester@lsces.co.uk>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e015384be8722f60531a288f6
Subject: Re: [PHP-DEV] PHP Attributes -> docBloc alternatives ...
From: derokorian@gmail.com (Ryan Pallas)

--089e015384be8722f60531a288f6
Content-Type: text/plain; charset=UTF-8

On Fri, Apr 29, 2016 at 10:50 AM, Lester Caine <lester@lsces.co.uk> wrote:

> On 29/04/16 16:42, Rowan Collins wrote:
> > function foo($a) {
> > if ( $a < 42 ) { throw new Exception; } // Must not reach The Answer
> > ...
> > }
> >
> > vs
> >
> > <<test($a < 42)>> // Must not reach The Answer
> > function foo($a) { ... }
>
> The first version is my current code base, although it's unlikely to
> throw an exception, more likely to have already validated the data
> before using it so the check is redundant as it is already in the code
> to handle the problem data. But in the second example just where does
> the error redirect traffic? At least with in-line checks you control
> flow ... but just how do you add a range? Does that need different
> 'test' elements?
>
> My main target here IS to add a reliable mechanism to allow every
> variable to have it's own validation attributes. The only current route
> is as php-annotations nicely provided and which dovetails nicely into
> the existing documentation process. Simply adding comments in line is
> useless for the on-line documentation, and it's adding these annotations
> to the documentation in parallel with making the data available in the
> code which I'm trying to address. TRYING to find this even if it is
> commented in the code on 15 year old code is a problem, and being able
> to ADD docBloc annotation which can then be used later provides a
> practical way forward.
>
> I've no problem with an alternate annotation method ... as long as in
> PHP7 it is optional ... but I don't think this 'in-line' approach is
> ACTUALLY the right long term solution to data validation.
>

But his RFC is about adding meta-data, which can be used up to the USER.
The language here is providing no validation, just a means of defining
metadata,
which may in the future be expanded to some built in annotations. Validation
is not specifically the point of this RFC, and the fact that a system could
be built to provide this validation using the meta-data this RFC provides,
does not
limit it to that scope.


>
> --
> 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
>
>

--089e015384be8722f60531a288f6--