Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:94841 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 47041 invoked from network); 4 Aug 2016 21:59:47 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Aug 2016 21:59:47 -0000 Authentication-Results: pb1.pair.com smtp.mail=yohgaki@ohgaki.net; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=yohgaki@ohgaki.net; sender-id=pass Received-SPF: pass (pb1.pair.com: domain ohgaki.net designates 180.42.98.130 as permitted sender) X-PHP-List-Original-Sender: yohgaki@ohgaki.net X-Host-Fingerprint: 180.42.98.130 ns1.es-i.jp Received: from [180.42.98.130] ([180.42.98.130:39663] helo=es-i.jp) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 52/42-33134-2DAB3A75 for ; Thu, 04 Aug 2016 17:59:47 -0400 Received: (qmail 98564 invoked by uid 89); 4 Aug 2016 21:59:42 -0000 Received: from unknown (HELO mail-qt0-f178.google.com) (yohgaki@ohgaki.net@209.85.216.178) by 0 with ESMTPA; 4 Aug 2016 21:59:42 -0000 Received: by mail-qt0-f178.google.com with SMTP id 52so165865949qtq.3 for ; Thu, 04 Aug 2016 14:59:42 -0700 (PDT) X-Gm-Message-State: AEkoouv73SXAOBrPRZh0331PeFCCpDt4m0bH7UEOY8QG7bi3wActmT4H+EYZsZmdBxTnOwWeWD+oeehiVpc8Jw== X-Received: by 10.237.49.130 with SMTP id 2mr9549488qth.38.1470347976170; Thu, 04 Aug 2016 14:59:36 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.85.242 with HTTP; Thu, 4 Aug 2016 14:58:55 -0700 (PDT) In-Reply-To: References: <27c5add4-2c4c-bab1-6ca7-9c191917dd0e@gmail.com> <65975a09-1d96-c03b-ecb2-ab37d91e621c@gmail.com> Date: Fri, 5 Aug 2016 06:58:55 +0900 X-Gmail-Original-Message-ID: Message-ID: To: Rowan Collins Cc: "internals@lists.php.net" Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] Adding validate_var_array()/validate_input_array() to which version? From: yohgaki@ohgaki.net (Yasuo Ohgaki) Hi Rowan, On Fri, Aug 5, 2016 at 6:47 AM, Yasuo Ohgaki 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 yohgaki@ohgaki.net