<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED --- - GLSL preprocessor does not support expressions in #line"
href="https://bugs.freedesktop.org/show_bug.cgi?id=72273#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED --- - GLSL preprocessor does not support expressions in #line"
href="https://bugs.freedesktop.org/show_bug.cgi?id=72273">bug 72273</a>
from <span class="vcard"><a class="email" href="mailto:cworth@cworth.org" title="Carl Worth <cworth@cworth.org>"> <span class="fn">Carl Worth</span></a>
</span></b>
<pre>As discussed on the mailing list, my patches as sent allow an expression
for <line> but not for <source-string-number>.
But allowing expressions for both results in grammar ambiguities, (unless
we did something ugly like disallowing whitespace within these expressions).
I'm not sure what the right answer is, but my vote is to declare the GLSL
specification buggy here and stick with an implementation allowing only
integer literals.
I'll be happy to hear other ideas.
-Carl</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>