[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Public WebGL] getShaderInfoLog/getProgramInfoLog format specification
Let me just state by way of introduction in my usually offensively unproductive flamboyant manner: I'm really annoyed at this culture of "let's just half-arse it"
To illustrate why nobody is getting around translation and why you can't sweep it under the rug as "meh", here I quote the ESSL 1.00/3.00 standard (section 3.4):
#line must have, after macro substitution, one of the following two forms:
#line line source-string-number
where line and source-string-number are constant integer expressions.
The language contains a facility to provide line and file numbers (not filenames). It contains that facility in recognition that shaders are often composites of multiple files and snippets. In case we're not clear on that fact, here's some examples:
And in case there's any lingering doubt that translation is indeed what happens a lot, here's some examples of that:
To wit, I'm pretty sure that most of you have translation in your own utility code, and that none of you would want to be debugging your shaders (single or multi file) based on raw error logs as they come out.