18 Jul
2011
18 Jul
'11
5:25 p.m.
On Mon, Jul 18, 2011 at 1:17 PM, Mathias Gaunard <mathias.gaunard@ens-lyon.org> wrote:
On 18/07/2011 18:17, Beman Dawes wrote:
Boost.Filesystem needs the UTF-32 to UTF-16 and UTF-16 to UTF-32 adapters to implement char16_t and char32_t support. Do they have any known bugs or other outstanding problems?
Yes, they can read past the end of your input range if it contains invalid data at the end.
Interesting. Would a fix be difficult? Alternately, does your Unicode library in the sandbox have equivalent functionality, but without reading past the end on bad data? --Beman