Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:84161 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 78479 invoked from network); 2 Mar 2015 10:18:10 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 2 Mar 2015 10:18:10 -0000 Authentication-Results: pb1.pair.com smtp.mail=zeev@zend.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=zeev@zend.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 74.125.82.50 as permitted sender) X-PHP-List-Original-Sender: zeev@zend.com X-Host-Fingerprint: 74.125.82.50 mail-wg0-f50.google.com Received: from [74.125.82.50] ([74.125.82.50:39709] helo=mail-wg0-f50.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 0B/D4-48321-ED834F45 for ; Mon, 02 Mar 2015 05:18:09 -0500 Received: by wggx12 with SMTP id x12so32370167wgg.6 for ; Mon, 02 Mar 2015 02:18:03 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc:content-type; bh=XzliC+HUTG5UMlrbaznmkiOVzyDShvDGA0NzXM5uOMs=; b=kiomyNHnRT/dKzQ1sOV3F8ihU6fE5FH9KxkMnwsj/DjYj79+p69GkHZsyLax3rSBOM evoIh4+is1HuefP0JjJ6JQsmwnUpVLxujxACGf7AE6FdDg774LzQLEeE7bElgIw7Kiip BnSsVsKSSwPPywYAohIDFvxAPzS4J41i8tSsq2Mcg3epkoNLUZyxVSGbN9Wy2Cli95eM YKGj657/jdJ7t0PmrJyluGCv5oAfVBSr7xeMlPQZKbNELXtFGL8wyuFzAIoDGeuWytkJ 2OfZ50lksthNGaRvmVZzwP5BpV/6C9u3I+UrrDmHsALW8VJb8dZL9gGBkg/0KYTCpQzy XIPQ== X-Gm-Message-State: ALoCoQml43ZEtl+QzNf6uu+5KjbjvRPIwr4Wv80K6elDw1EZ3JZpi89DswOtiLWITS654Dl+KtGWnnjsDPMf7gS+J62Mcj+hzZrIllvT/pPgj90tRu9aUR7ljbaZCA9KsCHNJb+7ZeqZGriOceCQb2q4NvGeZhUCQA== X-Received: by 10.180.99.34 with SMTP id en2mr35016138wib.81.1425291482860; Mon, 02 Mar 2015 02:18:02 -0800 (PST) References: <54F42DDF.2070505@lsces.co.uk> <54F436E7.3060607@lsces.co.uk> In-Reply-To: <54F436E7.3060607@lsces.co.uk> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQHbEgvqZ08kgCvmYfG4mXODzCFejgD7DxroAZSg+X8CNOWwVQKzrIxQAbUm+uycqhRn0A== Date: Mon, 2 Mar 2015 12:18:01 +0200 Message-ID: <12b0175e25aa56d00717e8553e7ce368@mail.gmail.com> To: Lester Caine Cc: internals@lists.php.net Content-Type: text/plain; charset=UTF-8 Subject: RE: [PHP-DEV] Coercive STH - some real world tests and updated RFC From: zeev@zend.com (Zeev Suraski) > -----Original Message----- > From: Lester Caine [mailto:lester@lsces.co.uk] > Sent: Monday, March 02, 2015 12:10 PM > To: Zeev Suraski > Cc: internals@lists.php.net > Subject: Re: [PHP-DEV] Coercive STH - some real world tests and updated > RFC > > On 02/03/15 09:47, Zeev Suraski wrote: > > I'm obviously biased but I believe that the coercive rules actually > > cover a lot more ground than the weak+strict sets. In other words, > > with > > weak+strict, overall, you're going to have to add custom code in a lot > > weak+more > > cases than with the coercive rule set (either because weak is too weak > > and strict will very frequently be too strict, while coercive provides > > a rule-set that accepts sensible values and reject non-sensible ones, > > making it work out of the box in most cases). But even with coercive, > > it's definitely not a one size fits all solution, and it's not > > supposed to be either. You still have custom code available to you. > > But since the horse is now out of the stable, we have to live with strict > anyway, so where will coercive rules fit in if they get accepted as well? > All of > this is just creating different rules for sub-sets of users :( As Anthony proposed if both pass, we're going to have a vote to decide between them, as they do contradict each other. Note that we're not going to know the status of either vote with certainty until March 13th. Zeev