<feed xmlns='http://www.w3.org/2005/Atom'>
<title>jkc.git/src/uio.cc, branch WIP</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<id>https://git.spawned.biz/jkc.git/atom?h=WIP</id>
<link rel='self' href='https://git.spawned.biz/jkc.git/atom?h=WIP'/>
<link rel='alternate' type='text/html' href='https://git.spawned.biz/jkc.git/'/>
<updated>2025-09-22T21:38:21Z</updated>
<entry>
<title>Change io::Reader and company to return ReadError::Eof instead of 0.</title>
<updated>2025-09-22T21:38:21Z</updated>
<author>
<name>Joel Klinghed</name>
<email>the_jk@spawned.biz</email>
</author>
<published>2025-09-22T21:38:21Z</published>
<link rel='alternate' type='text/html' href='https://git.spawned.biz/jkc.git/commit/?id=ce271f82f16ee89a18e7bfc9ed8eab7cbd6f37bc'/>
<id>urn:sha1:ce271f82f16ee89a18e7bfc9ed8eab7cbd6f37bc</id>
<content type='text'>
It's debatable if Eof should be considered an error or not.
But it is pretty clear it generally is a special response that
needs special handling, so easier to keep with the unexpected lot.

Also keeps better at higher abstraction levels, such as the line
reader.
</content>
</entry>
<entry>
<title>fixup! uio: Unicode reader</title>
<updated>2025-09-17T21:35:49Z</updated>
<author>
<name>Joel Klinghed</name>
<email>the_jk@spawned.biz</email>
</author>
<published>2025-09-17T21:35:49Z</published>
<link rel='alternate' type='text/html' href='https://git.spawned.biz/jkc.git/commit/?id=8e58293ef954d307875019c9a20eaee7dc7a3ed2'/>
<id>urn:sha1:8e58293ef954d307875019c9a20eaee7dc7a3ed2</id>
<content type='text'>
</content>
</entry>
<entry>
<title>uio: Remove unnecessary wrappers</title>
<updated>2025-09-16T22:05:42Z</updated>
<author>
<name>Joel Klinghed</name>
<email>the_jk@spawned.biz</email>
</author>
<published>2025-09-16T22:05:42Z</published>
<link rel='alternate' type='text/html' href='https://git.spawned.biz/jkc.git/commit/?id=d091dc78154d1c6341251f1ed13bfe3b33f10773'/>
<id>urn:sha1:d091dc78154d1c6341251f1ed13bfe3b33f10773</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add .clang-format</title>
<updated>2025-09-15T19:15:53Z</updated>
<author>
<name>Joel Klinghed</name>
<email>the_jk@spawned.biz</email>
</author>
<published>2025-09-15T19:15:53Z</published>
<link rel='alternate' type='text/html' href='https://git.spawned.biz/jkc.git/commit/?id=aa49abdf239bae6065fddd0839ec67a404c9748c'/>
<id>urn:sha1:aa49abdf239bae6065fddd0839ec67a404c9748c</id>
<content type='text'>
Make it easier to keep a consistent style
</content>
</entry>
<entry>
<title>uio: Unicode reader</title>
<updated>2025-09-15T18:52:51Z</updated>
<author>
<name>Joel Klinghed</name>
<email>the_jk@spawned.biz</email>
</author>
<published>2025-09-15T18:52:51Z</published>
<link rel='alternate' type='text/html' href='https://git.spawned.biz/jkc.git/commit/?id=18a622f378b403788c67fc785d30f4609caa3fc7'/>
<id>urn:sha1:18a622f378b403788c67fc785d30f4609caa3fc7</id>
<content type='text'>
Reads UTF-8 and UTF-16 into UTF-8 or UTF-16 strings.
If strict is true, fails at first invalid character.
If strict is false, invalid characters are replaced with U+FFFD.
For the replacement, I changed behavior if uN::read_replace to only
jump one byte. Otherwise a common invalid case when ISO-8859-1 or
WIN-1252 are read as UTF-8 would skip many characters.

If skip_bom is true any bom at start of stream is ignored.
If skip_bom is false any bom will be included.

Input format can be forced, if not detect is used which will
try to guess and then fallback to UTF-8.
</content>
</entry>
</feed>
