Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129194
Precedence: list
MIME-Version: 1.0
References: <CAOV5rgZjxhe+75YD13wWFRNghbS4fbUrJVouPtbUv9RdpKSAXw@mail.gmail.com>
 <348856E5-6A4E-455A-81AE-882832170168@rwec.co.uk> <CAOV5rgaKkR-y3Hu9Fs0_ty2wT5MoYLDJ_OTH-nDBA-g__t4VEA@mail.gmail.com>
 <AE53E18F-A195-4D40-8BD1-D75AAFE07F92@rwec.co.uk> <CAOV5rgYNXLvBaBW50KpzNTFC7wEVBC0+QdSPmKhqsdGyc3uPWQ@mail.gmail.com>
 <38e57171-fc2e-4d79-8614-0b1c5a2efc72@app.fastmail.com> <CAOV5rgbCVFHPivdKn7oWbKbOD9yaGXu2h5jgoGg9vmBz=mq3Gw@mail.gmail.com>
 <e0a9d131-f24d-4d0d-83f9-08f023530d21@app.fastmail.com> <CAOV5rgaCbUmSsh=YGPtbvijOa+fCZKMPudGnzhThCg54tt89FA@mail.gmail.com>
 <CAPhkiZz4951RNix1pH+kAk0EbOTN6icj0Q3NkV59cG8heuMjSg@mail.gmail.com>
 <CAOV5rgaWhAj23ojzt8cU4sYcZhzqsdHZP4Pn9BQcMUjJR1VYfA@mail.gmail.com> <CAPhkiZyUjouihk_QM8XZQcbxPLe02U-Td26kUqA79xcmnA1GZw@mail.gmail.com>
In-Reply-To: <CAPhkiZyUjouihk_QM8XZQcbxPLe02U-Td26kUqA79xcmnA1GZw@mail.gmail.com>
Date: Tue, 11 Nov 2025 11:14:25 +0100
Message-ID: <CAOV5rgZxteac8ZZvWTSNiJVB7epJp=4TfRdLOj8EAnOMEXKOpA@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC][DISCUSSION] Add RFC 4648 compliant data encoding API
To: Andrey Andreev <narf@devilix.net>, PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000003fc6e406434eea42"
From: nyamsprod@gmail.com (ignace nyamagana butera)

--0000000000003fc6e406434eea42
Content-Type: text/plain; charset="UTF-8"

Hi all,

Since my last reply I have updated the RFC:

   - RFC Text: https://wiki.php.net/rfc/data_encoding_api
   - Discussion Thread: https://news-web.php.net/php.internals/128069

The main changes are:

   - I added functions for base58 and base85 encoding;
   - For completeness, I introduced an error marker class (as per PHP
   policies
   <https://github.com/php/policies/blob/main/coding-standards-and-naming.rst#throwables>)
 and
   a specific exception to handle potential encoding errors;
   - I added examples to better explain the expected behaviours during
   string process;
   - I have updated the migration path from the current/legacy API to the
   newly proposed API;

Best regards,
Ignace

>

--0000000000003fc6e406434eea42
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">Hi all,<div><br></div><div>Since my last =
reply I have updated the RFC:</div><div><ul><li>RFC Text: <a href=3D"https:=
//wiki.php.net/rfc/data_encoding_api">https://wiki.php.net/rfc/data_encodin=
g_api</a></li><li>Discussion Thread: <a href=3D"https://news-web.php.net/ph=
p.internals/128069">https://news-web.php.net/php.internals/128069</a></li><=
/ul></div><div>The main changes are:</div><div><ul><li>I added functions fo=
r base58 and base85 encoding;</li><li>For completeness, I introduced an err=
or marker class (as per=C2=A0<a href=3D"https://github.com/php/policies/blo=
b/main/coding-standards-and-naming.rst#throwables">PHP policies</a>)=C2=A0=
=C2=A0and a specific exception to handle potential encoding errors;</li><li=
>I added examples to better explain the expected behaviours during string p=
rocess;</li><li>I have updated the migration path from the current/legacy A=
PI to the newly proposed API;</li></ul></div><div>Best regards,</div><div>I=
gnace</div></div><div class=3D"gmail_quote gmail_quote_container"><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex">
</blockquote></div></div>

--0000000000003fc6e406434eea42--