From: Felipe Magno de Almeida (felipe.m.almeida_at_[hidden])
Date: 2005-11-15 14:11:35
Please ignore this email, a typo in the disabling of the logs wasnt
disabling them.
As I've seen in the code, it is guarded by an if and it couldnt be
called any operator<< if the log is disabled.
BTW, I really liked the compile_time enabling of logs, very clever.
best regards,
On 11/15/05, Felipe Magno de Almeida <felipe.m.almeida_at_[hidden]> wrote:
> I've been profiling an application here where I work, that uses the
> logging library from John Torjo. With the logging disabled and using
> the
>
> LOG(logging_name) << (whatever to log) << ...
>
> The profiler shows that operator<< is using considerable CPU time
> (something like 10% of the application CPU time),
> so it seems that the current approach isnt sufficient.
> I'll probably need to create a macro that takes the logger and what to
> be logged and use somekind of if, just like the disabled cout example.
>
> best regards,
> --
> Felipe Magno de Almeida
> Developer from synergy and Computer Science student from State
> University of Campinas(UNICAMP).
> Unicamp: http://www.ic.unicamp.br
> Synergy: http://www.synergy.com.br
> "There is no dark side of the moon really. Matter of fact it's all dark."
>
-- Felipe Magno de Almeida Developer from synergy and Computer Science student from State University of Campinas(UNICAMP). Unicamp: http://www.ic.unicamp.br Synergy: http://www.synergy.com.br "There is no dark side of the moon really. Matter of fact it's all dark."