On 23 Nov 2019, at 2:11 am, Stephan Bergmann <sbergman@redhat.com> wrote:
On 22/11/2019 14:55, Luboš Luňák wrote:
SAL_LOG=+INFO.sal.osl-INFO.sal.osl.noisyarea . Problem solved :).
Sure, if one is willing to invest in adding sal.osl.noisyarea and reclassifying existing uses.
Which is typically not the case when you do a one-off SAL_LOG=... debug run. Which is where
judicious use of the facility by code authors pays off.
But this brings us back to the use case that you had identified - using SAL_LOG wasn’t the original
issue in the patch, incidentally, the issue was use of the tabs in the SAL_LOG. That appears to
have been the “misuse” of the logging facility.
Those who are trying to identify and resolve issues in EMF+ code are reliant on logging, so it does
seem to me that there is no other facility than SAL_LOG that we can use. I certainly don’t want to
litter the code with fprintfs to stderr.
Chris
Context
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.