<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - libwayland: the library should not print anything to stderr"
href="https://bugs.freedesktop.org/show_bug.cgi?id=73339#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - libwayland: the library should not print anything to stderr"
href="https://bugs.freedesktop.org/show_bug.cgi?id=73339">bug 73339</a>
from <span class="vcard"><a class="email" href="mailto:nfxjfg@gmail.com" title="nfxjfg@gmail.com">nfxjfg@gmail.com</a>
</span></b>
<pre>Well, you're almost there.
Remember how xlib had only a process wide error handler, and everyone hated it?
You're making the same mistake.
This is a very common mistake library designers do, and many libraries suffer
from this mistake - or rather, libraries using other libraries suffer from it,
because now they have to fight with other libraries for the log callback. That
everyone makes this error doesn't make it any less wrong.
I suggest that wl_log gets a context argument, and that the wl_log_handler can
be set per-context by the library user.
(Maybe this is less severe than the xlib issue, because wl_log_handler really
is only a log function and not more, but still.)</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>