[Webkit-unassigned] [Bug 195182] RELEASE_LOG should not be Cocoa specific

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=195182

Keith Rollin <krollin at apple.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |krollin at apple.com

--- Comment #1 from Keith Rollin <krollin at apple.com> ---
Just to provide some context, while the ultimate implementation may still be considered a mistake, it was something I gave some thought to.

The LOG macros and their underlying infrastructure were created (so I assume) for debugging at development time. The circumstances under which that logging is enabled and the disposition of that logging reflects that model. The logging is enabled on a channel-by-channel basis, and is streams to the terminal, Xcode console, or similar.

The RELEASE_LOG macros are for capturing information on a user's system so that it can be collected later for post-molten diagnosis. It's always-on, and is not streamed to an in-your-face console. Instead, it's stored in a combination of in-memory and on-disk databases.

Because of these two different models, use-cases, etc., I opted to keep the facilities separate, and to let the maintainers of other platforms provide whatever underpinnings for RELEASE_LOG that worked best for them. So rather than have RELEASE_LOG fall back onto LOG or its underlying facility, I'd see something new and platform-appropriate be added.

But that's just what I was thinking at the time. Others may have different opinions.

-- 
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/20190228/f6aab44a/attachment.html>