Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124700
Feedback-ID: id5114917:Fastmail
Message-ID: <caae7d17-27d9-4882-9ff0-f18f16433d2d@rwec.co.uk>
Date: Wed, 31 Jul 2024 22:13:45 +0100
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PHP-DEV] [RFC] [VOTE] Deprecations for PHP 8.4
To: internals@lists.php.net
References: <USzt7tZZlO1DmAbSTLhD-bqa23FqZn0zk2aah8Ndxgk9c7RY5PefQ8MjbYPUYAzr2_m4Cf-5AI4PuNBTS84rim_FNS6RaT-cWSv714HEvvU=@gpb.moe>
 <1a88918e-e808-d778-45e1-53797660e093@php.net>
 <CAPrKfG5Cw_nU7g7FR+t4C1-YZ8CDsDO_-sRs=yEsHO5kCTZL+A@mail.gmail.com>
 <95147d9d-d6e8-4396-bf0b-409c33679f90@bastelstu.be>
 <CAPrKfG4TijmZ_N9512_Fk9MBUNg=E6PjNTy-bCbV8CAj9_wX8A@mail.gmail.com>
 <CAPrKfG7Hi0SGbLA31V-9KjHM50QaX+Q=PptuO4+VMOrz7d9eBA@mail.gmail.com>
 <G9IiDe18a2ZhrXPA-zljNZsawKCZxlTn2ACfJpM32scdRkRflZ2rM6Ra8z88ZYDczomex4pffxZMpVhEjdB74YQXXNyqJkd7rQdDGA14HC0=@gpb.moe>
 <89096756-9f50-4b10-9630-d3b18e4b9c29@gmx.de>
 <d54b99fd-64ea-40f2-9fee-c904f1305893@app.fastmail.com>
 <3beb3488-94fc-484e-ac6c-ce7a7a0facd2@app.fastmail.com>
 <70262e95-f0e7-40c0-a731-480f178cbc35@bastelstu.be>
Content-Language: en-GB
In-Reply-To: <70262e95-f0e7-40c0-a731-480f178cbc35@bastelstu.be>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
From: imsop.php@rwec.co.uk ("Rowan Tommins [IMSoP]")

On 30/07/2024 20:15, Tim Düsterhus wrote:
> Part of the motivation of the deprecation (and my argument against the 
> addition of a standalone sha256() function) is simplifying the 
> documentation: Everything needs to be written down in multiple 
> different places, any changes to hash_file() will likely also need to 
> be applied to md5_file() and sha1_file() - and then it will need to be 
> translated.


We already have a solution for this: named snippets (implemented as XML 
entities), which exist in the source once, are translated once, and then 
inserted into every page that applies when it's rendered to HTML.

For instance, the yellow "Caution" box on pages like 
https://www.php.net/rand is defined once in "language-snippets.ent", and 
can be inserted into any page with &caution.cryptographically-insecure;


>
> Given that the md5(), sha1(), md5_file(), and sha1_file() functions 
> are not part of the hash extension, it's also much harder for the user 
> to discover the incremental hashing functionality provided by 
> hash_init(). 


Again, that seems easily solved: ext/hash is now always-on, so moving 
the functions there from ext/standard would have no effect on users.


-- 
Rowan Tommins
[IMSoP]