Subject: Re: [boost] loglite - A logging library (JD)
From: Emil Dotchevski (emildotchevski_at_[hidden])
Date: 2009-10-29 12:28:17
On Wed, Oct 28, 2009 at 11:44 PM, Tan, Tom (Shanghai) <TTan_at_[hidden]> wrote:
>> Please have a look and let me know what you think could be improved.
> The first thing I notice is that it does not support std::wstring
> directly. It's a big problem in my case I use wide-character in all my
> applications, which simplifies dealing with UTF-16 adopted by Modern
> Windows platforms.
> If I need to any string info from my program, I'll have to convert from
> UTF16(represented as std::wstring) to UTF8 so that it could be working
> well with LOGLITE. That's inconvenient.
OTOH, if you are targeting any other platform in addition to Windows,
it probably makes more sense to adopt UTF-8 throughout your program
and convert to UTF-16 before calling Windows functions.
> Offtopic, I am expecting boost::filesystem V3 for this very same reason.
Way offtopic, I also find path/wpath problematic. In my mind, their
invariant doesn't differ enough from that of string/wstring to justify
coupling my interfaces with boost::filesystem. So I use UTF-8
string/char const * in my code on all platforms, and use
boost::filesystem as an implementation detail, through wrappers that
take UTF-8 strings.
Reverge Studios, Inc.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk