slipher
slipher
This should go into a for-x.y.z branch so that developers can keep working on master without having to acquire new assets. Is there supposed to be any user-visible change from...
My recollection is that it turned out that vendors didn't bother to implement GL_PROXY correctly, so using it was a bad idea.
The existing "include" method (vertexInlines/fragmentInlines) uses the `#line` directive so that compiler errors have the right line number. It would be nice to have that here too (and also `#file`...
OK, I thought it would be easy to add an example since once of the fragmentInlines/vertexInlines could be trivially replaced with a `#insert` but maybe I'm wrong.
> > The existing "include" method (vertexInlines/fragmentInlines) uses the `#line` directive so that compiler errors have the right line number. It would be nice to have that here too (and...
I was thinking mainly to have the line directive _after_ the insertion, to maintain correct line numbers for the main file. So `#line 61` in your example. Additionally adding line...
Actually if you have an insert on line 60, maybe the best thing would be to put `#line 59` before every single line so the user will know any error...
> > Is having a 4KB large fragmentBuffer_t struct really faster than using variable-size arrays? Allocation can be slow but having to split up the socket reads/writes (since the amount...