Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:97843
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.44 as permitted sender)
MIME-Version: 1.0
References: <CAESVnVqidtzAdpKG5B-jo_hCSPyo4F-VVnj1zh-PcOUTkHY9Sg@mail.gmail.com>
In-Reply-To: <CAESVnVqidtzAdpKG5B-jo_hCSPyo4F-VVnj1zh-PcOUTkHY9Sg@mail.gmail.com>
Date: Wed, 18 Jan 2017 00:00:20 +0000
Message-ID: <CAPwsocG6JMnZxc318h7KENYpg8YKcD1oOYFqCGLj8M1BDrWGVA@mail.gmail.com>
To: Sara Golemon <pollita@php.net>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=94eb2c1cd198e4b8000546531a62
Subject: Re: [PHP-DEV] [RFC][Vote] HashContext using Objects
From: leight@gmail.com (Leigh)

--94eb2c1cd198e4b8000546531a62
Content-Type: text/plain; charset=UTF-8

On Tue, 17 Jan 2017 at 22:49 Sara Golemon <pollita@php.net> wrote:

> Voting has opened on: https://wiki.php.net/rfc/hash-context.as-resource
>
> Voting will remain open for two weeks and will close on 31 Jan, 2017
> at 23:59:59 UTC
>
> -Sara
>

Thanks for the work on this.

I've voted for frozen behaviour because I feel like the continued use of a
context is more likely to be a bug than intentional behaviour.

It's also more in-line with crypto code I'm familiar with, a finalised
context is finalised.

--94eb2c1cd198e4b8000546531a62--