[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Public WebGL] getShaderInfoLog/getProgramInfoLog format specification



On Thu, Jan 8, 2015 at 8:37 AM, Gregg Tavares <khronos@greggman.com> wrote:
Referring back to the mobile limiting extension idea this again seems far better implemented as a _javascript_ library. Either take ANGLE and compile it with emscripten or write a new parser. There's no reason to bloat the spec and bloat browsers with this stuff.

And just like before, you can continue to add more and more features whenever you want without having to wait for 4, 5 or 6 browser teams to find the time to do it for you. You won't need to argue here about which format should be supported (text, JSON? XML?)  and whether it it be internationalized or which warnings to include vs errors and which other features you want. If you want a feature add it, if you can't agree fork it.

You could even easily expand that into some kind of uber shader debugger that re-wrote/re-compiled the shaders on the fly as you try to step through them.

The ESSL language specification already specifies delivery by the programmer of file and line numbers. It's only reasonable to ask that there be a facility to reliably retrieve those numbers again. See: half-arsing it.