From: Jacob Moody <moody@posixcafe.org>
To: 9fans@9fans.net
Subject: Re: [9fans] Why does utfutf() exist?
Date: Thu, 18 Dec 2025 14:48:21 -0600 [thread overview]
Message-ID: <78235902-516a-4256-867d-37e7f57c24a5@posixcafe.org> (raw)
In-Reply-To: <CAKzdPgzdZV1y4GsexeGTeYahoY8=8SnOeBxK3dvAqGWAF8At9w@mail.gmail.com>
On 12/18/25 14:16, Rob Pike wrote:
> It was written for UTF (sic), not UTF-8, which was non-synchronizable and therefore ambiguous so care needed to be taken when looking for byte sequences. It stayed around after that. It may not be necessary, although without checking I can't say whether it behaves the same as strstr when illegal UTF-8 encodings occur.
>
Thanks! That makes sense.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T8831073f8b8bb351-M65fc39da67f62ef7c3b081e6
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
prev parent reply other threads:[~2025-12-18 21:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 21:17 [9fans] Why does utfutf() exist? Jacob Moody
2025-12-18 9:53 ` Shawn Rutledge
2025-12-18 15:50 ` quiekaizam via 9fans
2025-12-18 17:13 ` Jacob Moody
2025-12-18 20:16 ` Rob Pike
2025-12-18 20:48 ` Jacob Moody [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=78235902-516a-4256-867d-37e7f57c24a5@posixcafe.org \
--to=moody@posixcafe.org \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).