Re: [boost] Boost.Logging hex dumps (Was: Boost.Logging:formalreview)

From: Gennadiy Rozental (gennadiy.rozental_at_[hidden])
Date: 2005-11-15 17:12:49

"Pavel Antokolsky aka Zigmar" <zigmar_at_[hidden]> wrote in message 
news:b9e625b70511151325g7c4820e2l36b7766177b8fac3_at_mail.gmail.com...
> On 11/15/05, Gennadiy Rozental <gennadiy.rozental_at_[hidden]> wrote:
>> >> For example, in some cases I do not want to print non-ascii
>> >> characters in hex dump, in others I do.
>> > ? How does a hex dump contain anything other than hex digits and space 
>> > (to
>> > separate bytes).
>> > You might want a way of controlling whether to use upper or lower case
>> > letters (but I wouldn't bother).
>>
>> In my case I follow format presented by some text editors I am used to. 
>> It
>> includes both hex and actual data on the right. But I wouldn't insist 
>> that
>> much on this particular one.
> It's ok, but only in some cases. For example, less sophisticated
> editors go crazy, when trying to display non-ascii characters. And
> when output contains new line symbols and  zeroes the log becomes a
> mess.

You are not required to use it. You are always at liberty to write your own 
manipulators.

> I'm not telling that isn't useful (I use it myself from time to time),

Just as many other log library users.

Gennadiy