<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTOURBUG - Second Life shaders fail to compile" href="https://bugs.freedesktop.org/show_bug.cgi?id=71591#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTOURBUG - Second Life shaders fail to compile" href="https://bugs.freedesktop.org/show_bug.cgi?id=71591">bug 71591</a> from <a class="email" href="mailto:eero.t.tamminen@intel.com" title="Eero Tamminen <eero.t.tamminen@intel.com>"> Eero Tamminen</a> <pre>Giving an error when the extension changes behavior of existing functionality can be useful for developers, as such things may cause grief for them. For anything else, it's the error itself that causes grief. Options for fixing this issue are: - changing all errors about this to warnings - making the error extension specific: outputting it only for behavior changing extensions - adding a config option for whether this gives an error or not. Default config could then disable this error for binaries that are known to use extension declarations in wrong place. How common this issue is, what other programs have this issue besides Second life client, photoshop, and Unigine Heaven benchmark? And what extensions those declare in wrong place?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>