$include_dir="/home/hyper-archives/boost/include"; include("$include_dir/msg-header.inc") ?>
From: Daniel James (daniel_at_[hidden])
Date: 2005-03-19 06:20:03
Felipe Magno de Almeida wrote:
> I think it would be desireble to have the dynamic class even when not
> having such iostream functionality. Sometimes we dont know which utf we
> are going to use, even when needing to read it from somewhere else or
> making it through some low-level way. But having iostreams read and
> write unicode would be awesome. Maybe having somekind of stringstream
> would be great too, but I think it would be much more work than it was
> planned.
Why should such a string class stop at unicode? Wouldn't it be a good
idea to support other encodings? It might be better to have such a class
as part of a separate library, probably with 'pluggable' encodings,
which would include unicode.