Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:71425
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 85.214.73.107 as permitted sender)
Message-ID: <3c4d384aa24ec577947ef109bd77757b.squirrel@webmail.klapt.com>
In-Reply-To: <52E01DDA.4020404@oracle.com>
References: <d27df615bc27d701daceb5ee605f540f.squirrel@webmail.klapt.com>
    <2ecdbcfc1725e25ccad4705429dbfa2f.squirrel@webmail.klapt.com>
    <52E01DDA.4020404@oracle.com>
Date: Thu, 23 Jan 2014 09:47:16 +0100
To: "Christopher Jones" <christopher.jones@oracle.com>
Cc: "PHP internals" <internals@lists.php.net>
Reply-To: "Anatol Belski" <ab@php.net>
User-Agent: SquirrelMail/1.5.2 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=UTF-8
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] [RFC] 64 bit improvements, open questions
From: ab@php.net ("Anatol Belski")

Hi Chris,

On Wed, January 22, 2014 20:36, Christopher Jones wrote:
> The open issues (e.g. SAPI support) need to be resolved before
> starting the vote, so the RFC direction is obvious.  Also the RFC needs to
> discuss proposed voting options, prior to starting the vote. Since that
> only gives a couple of days for discussion, I think you should delay the
> vote.
I'm not sure taking SAPI and ZPP topics out of the scope apart into new
RFCs would make any sense? But we probably can do multple votings in the
same RFC. That will be probably the most plausible solution to decide, I
gonna to update it :)

> The porting doc compat/PECL_PORTING should be merged into the RFC (and
> removed from the tree) to capture as much information in the one place as
> possible.
>
I thought more like pick it out into a separate wiki page, as it's porting
specific. Still it will be linked from/to RFC, but the structure were
cleaner IMHO.

Regards

Anatol