Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79479
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.177 as permitted sender)
Message-ID: <5485FF34.1050305@gmail.com>
Date: Mon, 08 Dec 2014 20:42:44 +0100
User-Agent: Thunderbird
MIME-Version: 1.0
To: internals@lists.php.net
References: <790a8d7299a7cda01ee76d8293b7d5af.squirrel@webmail.klapt.com>    <CAEZPtU5TEo8w6gwHpEJSPLtirPD9eiMGdCNG=YosQLPvN894ow@mail.gmail.com> <d332ef4329997b2d51464dfc0a1abc05.squirrel@webmail.klapt.com>
In-Reply-To: <d332ef4329997b2d51464dfc0a1abc05.squirrel@webmail.klapt.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Native TLS
From: keisial@gmail.com (=?UTF-8?B?w4FuZ2VsIEdvbnrDoWxleg==?=)

On 03/12/14 10:22, Anatol Belski wrote:
> I meant that as well, to the time it's merged all the TSRMLS_* thingies
> should be removed. I kept them only while developed and now for the RFC so
> the diff shows the only change done, otherwise it would sink in the
> unrelevant stuff.
>
> Therefore I'd rather stay by the yes/no choice as removing TSRMLS_* is the
> essential part of the RFC - so better at once then :) As otherwise one can
> sure find some factor to defer the actual change, but the change is the
> actual goal.
>
> Regards
>
> Anatol

It seems quite clear to me:
1. Change the code.
2. Remove the TSRMLS_* macros from the code in a subsequent commit
3. Leave the no-op macros at an unused header for a few releases, for 
the benefit of porting extensions / extensions targetting several versions.