Hi Rowan, On Fri, Aug 5, 2016 at 6:47 AM, Yasuo Ohgaki <yohg...@ohgaki.net> wrote: >> I know naming things is hard, but I really do think "validation" is not the >> correct name for what you are talking about. Search online for "form >> validation", and you will see what I mean. >> >> The correct response to a form validation error is to show a message to the >> user with as much detail as possible, not to simply terminate the script and >> assume they are trying to attack your application. > > We are talking about different things. > I'll document it clearly in RFC.
Different function name may help to avoid confusions. How about filter_assert_*() (I'm using filter_ prefix suggested by Pierre. It's few chars longer, but better consistency :) These functions could be used for input mistake/error checks, but I would like to users to use them only to assert external inputs, see if valid(acceptable) or invalid(unacceptable) for the software. The name may help. Hopefully. Regards, -- Yasuo Ohgaki yohg...@ohgaki.net -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
