Programming

20958 readers

106 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 2 years ago

MODERATORS

[email protected]

Lukas Atkinso: Net-Negative Cursor (lukasatkinson.de)

submitted 2 weeks ago* (last edited 2 weeks ago) by [email protected] to c/[email protected]

12 comments fedilink hide all child comments

What I think in addition to what Atkinso writes: If you just strip arbitrary bytes that happen to be equal in value to the numeric value of ASCII control characters or whitespace, how can you be sure that you don't destroy valid non-whitespace unicode symbols?

You can't! This will work only of you have actually ASCII input.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 6 points 2 weeks ago (7 children)

In UTF8, all bytes that are not an ASCII character have the high bit set.

[–] [email protected] -2 points 2 weeks ago (5 children)

You are right with this. But still, in Rust, a vector of u8 is different from a sequence of unicode characters. This would not work in Python3 either, while it'd work in Python2.

[–] [email protected] 2 points 2 weeks ago* (last edited 2 weeks ago) (2 children)

~~yeah it's incorrect bc it destroys multibyte characters, but~~ no idea what you're saying about u8 being a different type from unicode. the original code was reading bytes and converting them too? the typing isn't the issue, you can still store utf8 as a series of bytes

[–] [email protected] 1 points 2 weeks ago (1 children)

it's incorrect bc it destroys multibyte characters

It doesn't. As the poster two levels up said, all bytes that don't represent an ASCII character have the high bit set, even the follow-up bytes in multibyte sequences. So the condition b >= 32 will match and preserve them.

[–] [email protected] 4 points 2 weeks ago

yeah fair enough. that wasn't really my point and I wasn't paying attention

load more comments (2 replies)

load more comments (3 replies)