<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Inconsistent use of both stderr and stdout for debug output"
href="https://bugs.freedesktop.org/show_bug.cgi?id=65475#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Inconsistent use of both stderr and stdout for debug output"
href="https://bugs.freedesktop.org/show_bug.cgi?id=65475">bug 65475</a>
from <span class="vcard"><a class="email" href="mailto:idr@freedesktop.org" title="Ian Romanick <idr@freedesktop.org>"> <span class="fn">Ian Romanick</span></a>
</span></b>
<pre>It seems like most of the messages should use one of _mesa_problem,
_mesa_error, or _mesa_warning. We may even want an additional _mesa_info. The
advantage of using these (instead of printf directly) is they also route
through ARB_debug_output.
printf and fprintf appear ~1500 times in the code base. Going through and
changing all of them (and reviewing all the patches that result), doesn't seem
like a good use of anyone's time. :(</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>