<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED --- - replace tools/solar.h macros with osl versions"
href="https://bugs.freedesktop.org/show_bug.cgi?id=63154#c58">Comment # 58</a>
on <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED --- - replace tools/solar.h macros with osl versions"
href="https://bugs.freedesktop.org/show_bug.cgi?id=63154">bug 63154</a>
from <span class="vcard"><a class="email" href="mailto:sbergman@redhat.com" title="Stephan Bergmann <sbergman@redhat.com>"> <span class="fn">Stephan Bergmann</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=63154#c57">comment #57</a>)
<span class="quote">> I understand your point of view, and probably it's the best idea. It's wrong
> to put sal_uLong definition in sal/types.h?</span >
Yes, that's wrong. sal_uLong is a "temporary" hack for a problem in code
"above" the URE interface, so it should not find its way into the URE stable
interface.
Looks like there is a handful things (SVLIBRARY. sal_uLong) that best stay in
tools/solar.h for now, even if that means that tools/solar.h cannot be removed
completely for now.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>