Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:87240 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 38655 invoked from network); 22 Jul 2015 22:38:24 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Jul 2015 22:38:24 -0000 Authentication-Results: pb1.pair.com header.from=ua.san.alex@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=ua.san.alex@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.172 as permitted sender) X-PHP-List-Original-Sender: ua.san.alex@gmail.com X-Host-Fingerprint: 209.85.223.172 mail-ie0-f172.google.com Received: from [209.85.223.172] ([209.85.223.172:35306] helo=mail-ie0-f172.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D8/C7-27316-F5B10B55 for ; Wed, 22 Jul 2015 18:38:23 -0400 Received: by iecri3 with SMTP id ri3so83881574iec.2 for ; Wed, 22 Jul 2015 15:38:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=ZhEdOe7BiezfVsXn+8aS/hyLFJtS6EoqtjkIT/dvKV4=; b=XelbiLQ/DtCLOug8S0Jgxucwad6nTAwSbVNosTUIdTFpJtHXR8fJFgu2RL8RKCRb7i w1Q+2Z1L9LYzTRPl2uJmek6nXeSy3IncTxRx3mJgiyKaZy0eI5jfn5/uHsAvXCaWIUoT tAlYxuwCmmLdVtCcJiIpmugvumN0o2rDd0pjzWpJN6Ys/htBV8RIR1X49MD+g+eBD3d5 uU3XNhtvvpL9v4nolawEC/wqvXes/qGesG2U7Czbh+1NP72JogfAKjlJD9drWGNnS8LB yQGN0qP7PgQts3xb9kGHpVmvngZ+JEKCLcdPdO5w2ndplA+T1eXHUzyrTxceFz4ypwQh Le2w== MIME-Version: 1.0 X-Received: by 10.107.37.14 with SMTP id l14mr8833925iol.12.1437604700839; Wed, 22 Jul 2015 15:38:20 -0700 (PDT) Received: by 10.50.246.20 with HTTP; Wed, 22 Jul 2015 15:38:20 -0700 (PDT) In-Reply-To: References: Date: Thu, 23 Jul 2015 01:38:20 +0300 Message-ID: To: Patrick ALLAERT Cc: marcio3w@gmail.com, Yasuo Ohgaki , PHP internals Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] Re: Voting choice for language changes (Was: "Re: [PHP-DEV][RFC][DISCUSSION] Strict Argument Count") From: ua.san.alex@gmail.com ("S.A.N") I am satisfied, the possibility of group declarations, but the that lack: Unfortunately have to write so: It looks ugly and very strange. My proposition, the imported end name, if end of without slash. Like this: 2015-03-11 11:08 GMT+02:00 Patrick ALLAERT : > Le mar. 10 mars 2015 =C3=A0 19:29, Marcio Almada = a > =C3=A9crit : > >> Hi, >> >> 2015-03-10 11:39 GMT-03:00 Patrick ALLAERT : >> >> Hello, >>> >>> Le ven. 6 mars 2015 =C3=A0 00:44, Marcio Almada = a >>> =C3=A9crit : >>>> >>>> You are right about this. I'll setup a yes/no vote + a vote to decide >>>> between E_WARNING (for consistency), E_DEPRECATED or E_STRICT. For me >>>> this >>>> is just a detail but maybe it's very important to others, so better to >>>> let >>>> each voter decide upon it. >>>> >>> >>> In case of language changes, shouldn't the 2/3 of majority be required = at >>> any levels? >>> >>> >> I don't think it's possible. What would happen if the yes/no vote passes >> but the secondary vote doesn't reach 2/3 for some option? This would be = a >> weird situation. >> > > Pretty simple actually: it would simply not pass because it wouldn't gath= er > enough support. > > Discuss the options, see what gather the most support and the better > reasonings and then suggest that the RFC "yes" vote means A, B or C while > summarizing the reasons of the choice for it in the RFC itself. > > A language change vote requiring 2/3 majority on a Yes/No and a simple > majority in an option basically means not requiring 2/3 at all, but 50% > (with 2 options) at most!