<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Fixed compilation with !ENABLE(SVG_FONTS)."
href="https://bugs.webkit.org/show_bug.cgi?id=156850#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Fixed compilation with !ENABLE(SVG_FONTS)."
href="https://bugs.webkit.org/show_bug.cgi?id=156850">bug 156850</a>
from <span class="vcard"><a class="email" href="mailto:ossy@webkit.org" title="Csaba Osztrogonác <ossy@webkit.org>"> <span class="fn">Csaba Osztrogonác</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=156850#c3">comment #3</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=156850#c2">comment #2</a>)
> > We prefer guarding source files to guarding build sytem when it is possible.
>
> It's the opposite of what we've been doing recently. Maybe we should discuss
> this on webkit-dev?</span >
What do you mean? I haven't seen any patch removing if guards from source file.
Source files are almost always guarded properly, I can't see a good reason
to break this good practice now. I think most of the build system guard
is redundant.</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>