Re: [Libreoffice-commits] "Use SAL_INFO instead of home-grown msgs_debug"

Stephan Bergmann <sbergman -AT- redhat.com>

Tue, 22 Jan 2013 15:58:32 +0100

On 01/19/2013 10:42 AM, Libreoffice Gerrit user wrote:

commit fcf7f3596054f24bebf767f9cabfc96dfa577480
Author: Tor Lillqvist <tml@iki.fi>
Date:   Sat Jan 19 10:44:33 2013 +0200

     Use SAL_INFO instead of home-grown msgs_debug

     If there is a need to optionally get a thread identifier or the
     function name into logging output (as msgs_debug did), we should
     figure out a way to do that in some elegant fashion in the sal logging
     macros instead of using some local solution in just one place in the
     code.

Note that SAL_INFO/WARN do include both a process ID and a thread ID in

their output.

Stephan

Context

Re: [Libreoffice-commits] "Use SAL_INFO instead of home-grown msgs_debug" · Stephan Bergmann

Re: [Libreoffice-commits] "Use SAL_INFO instead of home-grown msgs_debug" · Tor Lillqvist

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.