Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:84839
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain hotmail.com designates 65.55.111.92 as permitted sender)
Message-ID: <BLU436-SMTP63B4758D2D902644C6BB24E2050@phx.gbl>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 15 Mar 2015 16:50:36 +0100
To: PHP Internals <internals@lists.php.net>
MIME-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
Subject: [RFC] [INFO] Basic Scalar Types
From: bobwei9@hotmail.com (Bob Weinand)

Hey, to clarify what the way to go with this RFC is.

This RFC is a FALLBACK. It's about the common part of both other RFCs.
That way it *only* will go to vote after Anthonys RFC ends. And *only* =
if it fails.

That means, I will go by the voting RFC and wait until discussion period =
ends and put it to vote after Anthony closes his RFC in case it fails.

I'm aware that a few people have said, they will change their vote =
depending on what ever might pass. And that they asked for this RFC =
going into direct competition against Anthonys RFC. No. Know what you =
want. If you dislike Anthonys RFC, vote no on it. If you like it, vote =
yes on it. But don't switch your votes back and forth depending on what =
might win.
That's why I decided to not have the vote on this running concurrently =
with Anthonys.

But, in any case this RFC will go to vote on the 24th if Anthonys RFC =
couldn't gather a 2/3 supermajority.

Thanks,
Bob=