[Webkit-unassigned] [Bug 178276] New: [WPE][GTK] Unify/simplify/improve PAL::logLevelString, WebCore::logLevelString, and WebKit::logLevelString
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Fri Oct 13 11:49:13 PDT 2017
https://bugs.webkit.org/show_bug.cgi?id=178276
Bug ID: 178276
Summary: [WPE][GTK] Unify/simplify/improve PAL::logLevelString,
WebCore::logLevelString, and WebKit::logLevelString
Product: WebKit
Version: Other
Hardware: Unspecified
OS: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: Platform
Assignee: webkit-unassigned at lists.webkit.org
Reporter: aperez at igalia.com
We currently have:
- PAL::logLevelString (Source/WebCore/PAL/pal/unix/LoggingUnix.cpp)
- WebCore::logLevelString (Source/WebCore/platform/unix/LoggingUnix.cpp)
- WebKit::logLevelString (Source/WebKit/Platform/unix/LoggingUnix.cpp)
Essentially, the three do the same, which is:
1. Picking the value from the WEBKIT_DEBUG environment variable.
2. If the variable is not present, return an empty string.
3. If the variable is defined:
3.a. Warn with “WTFLogAlways” that some logging is only available
in debug builds.
3.b. Prepend “NotYetImplemented,” to the obtained value (except
for WebKit::logLevelString).
3.c. Return the value.
During a discussion with Konstantin Tokarev and Carlos López we came up
with the following possible improvements/doubts:
- Unifying all of them, by making both WebCore::logLevelString and
WebKit::logLevelString just call PAL::logLevelString.
- Removing the message emitted with WTFLogAlways().
- Does it make sense to always prepend “NotYetImplemented,”? Why was it
not being done for the WebKit version?
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20171013/5ba2cd65/attachment.html>
More information about the webkit-unassigned
mailing list