Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124885
Precedence: bulk
MIME-Version: 1.0
References: <CAPn3h8LunRRAEfQXbfuDzMsxwGeFZfsHXs7oB=DTMhN2fgphUg@mail.gmail.com>
In-Reply-To: <CAPn3h8LunRRAEfQXbfuDzMsxwGeFZfsHXs7oB=DTMhN2fgphUg@mail.gmail.com>
Date: Mon, 12 Aug 2024 12:33:03 +0200
Message-ID: <CAPzBOBOCHO069RPRMHTArv33ZkjOJiweqZpCd6iR12rvNE_XRQ@mail.gmail.com>
Subject: Re: [PHP-DEV][Discussion] Should All String Functions Become
 Multi-Byte Safe?
To: danielhaber@gmail.com
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary="00000000000042ef48061f7a0576"
From: landers.robert@gmail.com (Robert Landers)

--00000000000042ef48061f7a0576
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi,

Currently, PHP strings are binary safe (thus can store any encoding). I
generally think of PHP strings as being an array of bytes vs. a "string"
you are familiar with in other languages. The name is unfortunate in that
regard, but working with them is straightforward (imagine having an actual
array of bytes in PHP and trying to work on them).

Robert Landers
Software Engineer
Utrecht NL


On Mon, Aug 12, 2024 at 11:48=E2=80=AFAM <danielhaber@gmail.com> wrote:

> After reading Rowan's last message, it feels appropriate to link to this:
>
> "The Absolute Minimum Every Software Developer Must Know About Unicode in
> 2023 (Still No Excuses!)"
>
> https://tonsky.me/blog/unicode/
>
>
>

--00000000000042ef48061f7a0576
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:trebuche=
t ms,sans-serif">Hi,</div><div class=3D"gmail_default" style=3D"font-family=
:trebuchet ms,sans-serif"><br></div><div class=3D"gmail_default" style=3D"f=
ont-family:trebuchet ms,sans-serif">Currently, PHP strings are binary safe =
(thus can store any encoding). I generally think of PHP strings as being an=
 array of bytes vs. a &quot;string&quot; you are familiar with in other lan=
guages. The name is unfortunate in that regard, but working with them is st=
raightforward (imagine having an actual array of bytes in PHP and trying to=
 work on them).</div><div class=3D"gmail_default" style=3D"font-family:treb=
uchet ms,sans-serif"><br></div><div><div dir=3D"ltr" class=3D"gmail_signatu=
re" data-smartmail=3D"gmail_signature"><div dir=3D"ltr"><div><div dir=3D"lt=
r">Robert Landers<div>Software Engineer</div><div>Utrecht NL</div></div></d=
iv></div></div></div><br></div><br><div class=3D"gmail_quote"><div dir=3D"l=
tr" class=3D"gmail_attr">On Mon, Aug 12, 2024 at 11:48=E2=80=AFAM &lt;<a hr=
ef=3D"mailto:danielhaber@gmail.com">danielhaber@gmail.com</a>&gt; wrote:<br=
></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;=
border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">A=
fter reading Rowan&#39;s last message, it feels appropriate to link to this=
:<br><div><br>
</div><div>&quot;The Absolute Minimum Every Software Developer Must Know Ab=
out Unicode in 2023 (Still No Excuses!)&quot;</div><div><br>

</div><div><a href=3D"https://tonsky.me/blog/unicode/" target=3D"_blank">ht=
tps://tonsky.me/blog/unicode/</a></div><br><br></div>
</blockquote></div>

--00000000000042ef48061f7a0576--