search for: 1_45_0

...tf16 (i.e. wchar_t) internally on windows (ohterwise utf8). Then if a path is used multiple times no conversion takes place. The conversion only takes place at creation time when you create a path from utf8. even if you have reasons not to use it, you should have a look at www.boost.org/doc/libs/1_45_0/libs/filesystem/v3/doc/index.htm www.boost.org/doc/libs/1_45_0/libs/filesystem/v3/doc/v3_design.html -Jochen

On Fri, 26 Nov 2010 09:28:17 -0500 Michael Spencer <bigcheesegs at gmail.com> wrote: > On Fri, Nov 26, 2010 at 4:00 AM, Jochen Wilhelmy > <j.wilhelmy at arcor.de> wrote: > > No, this post was prompted since I switched to boost::filesystem > > version 3 in my own code and llvm/clang 2.8 > > was the only lib with no unicode support on windows. > > Will your

...depending on how long the conversion takes. Storing string as utf-16 would require changing them to utf-8 whenever the client wanted to look at them, incurring lots of memory allocations and copying. > even if you have reasons not to use it, you should have a look at > www.boost.org/doc/libs/1_45_0/libs/filesystem/v3/doc/index.htm > www.boost.org/doc/libs/1_45_0/libs/filesystem/v3/doc/v3_design.html > > -Jochen My design is based exactly off of that. - Michael Spencer