Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:112037
MIME-Version: 1.0
References: <CAJmy8YGSWkzEu1g2c9o=+5jSHEXGb=vW0dKcEwrHtKGPyC+eCA@mail.gmail.com>
 <ffa2774b-757e-879d-7bfa-dc554e4cc04a@gmx.de>
In-Reply-To: <ffa2774b-757e-879d-7bfa-dc554e4cc04a@gmx.de>
Date: Mon, 12 Oct 2020 16:01:20 +0200
Message-ID: <CADq_CxrGRb27DCH-jPDNOQaO7z+ka0bO-WfwhpgTQMp4aeys7A@mail.gmail.com>
To: "Christoph M. Becker" <cmbecker69@gmx.de>
Cc: Hans Henrik Bergan <divinity76@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000040ddd505b179bc30"
Subject: Re: [PHP-DEV] Re: want an Object-oriented interface for HashContext
From: robin@kingsquare.nl ("Kingsquare.nl - Robin Speekenbrink")

--00000000000040ddd505b179bc30
Content-Type: text/plain; charset="UTF-8"

Op ma 12 okt. 2020 om 14:55 schreef Christoph M. Becker <cmbecker69@gmx.de>:

> On 12.10.2020 at 13:49, Hans Henrik Bergan wrote:
>
> > something like
> >
> > $result = (new
> HashContext("SHA1"))->update($str1)->update($str2)->final();
> >
> > (userland sample imp: https://3v4l.org/lXd3u )
> >
> > I tried asking on the bugtracker ( https://bugs.php.net/bug.php?id=80221
> ) ,
> > but was told to ask on this mailing list instead.
>
> Thanks for bringing this up on the mailing list!
>
> I basically very much support a proper OOP interface, but I think the
> method names should use camel-case (e.g. ::updateFile() instead of
> ::update_file()), and it might be appropriate to rename ::final() to
> ::finalize().  More bikeshedding regarding the method names, and maybe
> their signatures might be in order.  We do not necessarily have to make
> these methods aliases of the existing functions, although that's of
> course possible.
>
>
Dear all,

As a user/developer of the language itself: it seems to me this is what a
package using composer could easily fix right? Does this really have to
land in core to be used in the wild? With the proliferation of all the up
and coming features and performance improvements it seems to me like these
types of improvements using lower level PHP interfaces / native functions
have no merit in core itself?
(packagist / composer packages don't always have to be full frameworks /
large solutions right IMHO)

This would also allow the developer to pick and choose a personal style and
we don't have to flood the internals with bikeshedding ;)

Robin Speekenbrink

--00000000000040ddd505b179bc30--