Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:95050
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.52 as permitted sender)
To: internals@lists.php.net
References: <10fbcb03-5de8-4d9a-da1c-7e2bf77937cb@lsces.co.uk>
 <CAEYWF=4kkvmp8TCmRhdhzzM-sWpk+-sYE7u2eP1Jf3NkshFiJA@mail.gmail.com>
 <CABdc3WqYeoXoHL-E4adjoZTVr1bs1CHfRaDmoqtmpGW7yREmUA@mail.gmail.com>
 <c76f0716-4881-4aae-2fbd-f1af70fd6114@lsces.co.uk>
 <CANUQDCjaXeJsCAjyE+q-UhXCFjexwRYWLKzMfwRQVDaEwVbLog@mail.gmail.com>
 <d67a6ee8-4fbe-9583-3bac-d2e98298663f@lsces.co.uk>
 <5657afc7-7569-5fc4-4a5a-27ed786c4fa5@gmail.com>
 <0825c173-5cb4-7f65-cf34-b45ca30919a3@lsces.co.uk>
 <8646c3ad-b929-cb0b-bad4-52a0a7160d16@gmail.com>
 <11ce571b-964b-5a3e-9f2f-3f69a8bc20b4@lsces.co.uk>
Message-ID: <7d9db8d5-ae7a-4123-14f4-f76fb6d764c5@gmail.com>
Date: Thu, 11 Aug 2016 23:17:50 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <11ce571b-964b-5a3e-9f2f-3f69a8bc20b4@lsces.co.uk>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Simple variable handling.
From: rowan.collins@gmail.com (Rowan Collins)

On 11/08/2016 21:19, Lester Caine wrote:
> No ... add more than just validation rules. Include facilities such as
> escape rules, display rules and variable specific material such as error
> messages.
>
> Just how the rules are enforced needs to be flexible and such things as
> 'required' will vary how the results are interpreted.

OK, so, again, you've mentioned plenty of the *why*, but what do you 
picture to be the *how*?

When would these various rules be applied? What might the code look like 
that relied on them?

You've mentioned a lot about flexibility, and that the feature could be 
used in multiple styles, but some concrete examples of how *you* would 
use it might help define what the feature needs to do (and not do).

Regards,

-- 
Rowan Collins
[IMSoP]