Re: [boost] filesystem question

On Fri, Jul 4, 2008 at 2:14 PM, Sebastian Redl
<sebastian.redl@getdesigned.at> wrote:
> Emil Dotchevski wrote:
>> What is the rationale for providing path and wpath types instead of
>> using a single path type?
> 1) Narrow encoding paths always existed, because the fstreams took narrow
> strings.
> 2) wpath was added later by request, I believe. Also, because the narrow
> encoding under Windows is never UTF-8 and thus can't ever represent all
> paths, and the NT and CE kernels natively use UTF-16 (wide characters).

Yes, we need the ability for path objects to store "narrow" and
unicode strings, and the ability to talk to the OS. This can be
achieved by a single path type and a few conversion functions, can it
not?

Emil Dotchevski
Reverge Studios, Inc.
http://www.revergestudios.com/reblog/index.php?n=ReCode