Skip to content

issues Search Results · repo:glslify/glsl-tokenizer language:JavaScript

Filter by

9 results
 (79 ms)

9 results

inglslify/glsl-tokenizer (press backspace or delete to remove)

glslify/glsl-tokenizer
String tokenizing expects 'eof'

Parsing a string sync results in a token stream that s expecting eof, which is only added in the streaming API. I don t think eof should be a token, since it s not in the glsl spec? https://www.khronos.org/files/opengles_shading_language.pdf ...
  • AndrewRayCode
  • Opened 
    on Nov 24, 2018
  • #15

glslify/glsl-tokenizer
Incorrectly parsing a } followed by a block comment.

Example: console.log(tokenizer( }/* foo */ )) Returns: A block-comment including the } and then an element of type undefined with the same data
  • DiThi
  • Opened 
    on Jul 4, 2017
  • #13

glslify/glsl-tokenizer
Layout Qualifiers

When 300 es is specified, it support parsing/tokenizing layout qualifiers for WebGL2 shaders: https://www.opengl.org/wiki/Layout_Qualifier_(GLSL)
  • mattdesl
  • Opened 
    on Feb 25, 2016
  • #11

glslify/glsl-tokenizer
test does not work

Hi! I’ve cloned and made npm install, but running tests fails with 2 errors: glsl-tokenizer: invalid characters √ does not hang! √ collects all expected operator characters tests 5 pass ...
  • dy
  • 5
  • Opened 
    on Feb 25, 2016
  • #9

glslify/glsl-tokenizer
5e-3

float test = 5.5e-3; is badly parsed as: [ { type: keyword , data: float , position: 0, line: 1, column: 5 } { type: whitespace , data: , position: 5, line: 1, column: 6 }, { type: ident , ...
  • dy
  • Opened 
    on Feb 25, 2016
  • #8

glslify/glsl-tokenizer
Duplicate builtins

The following builtin definitions occur twice in lib/builtins.js: - gl_Color - gl_SecondaryColor - gl_TexCoord - gl_FogFragCoord
  • tong
  • 1
  • Opened 
    on Nov 5, 2015
  • #5

glslify/glsl-tokenizer
GLSL ES 300

Changes at a glance: http://www.shaderific.com/blog/2014/3/13/tutorial-how-to-update-a-shader-for-opengl-es-30 - #version 300 es appears at top - texture2D - texture - attribute - in - gl_FragCoord ...
  • mattdesl
  • Opened 
    on Jun 24, 2015
  • #4

glslify/glsl-tokenizer
Approach to built-ins

Currently if a builtin isn t hard-coded it could break shaders (for example, fwidth not being listed might get mangled to fwidth_2_1). As WebGL2 and new extensions come to browsers, we should be wary of ...
  • mattdesl
  • 2
  • Opened 
    on Apr 5, 2015
  • #3

glslify/glsl-tokenizer
Builtin function as variable name seems legal

I don t know if this bug is in glsl-tokenizer or glsl-parser but float distance = 1.0; seems to not parse but is ok when compiling the GLSL. I don t know what the spec say about that, if it is legal? ...
  • gre
  • 1
  • Opened 
    on May 24, 2014
  • #1
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Restrict your search to the title by using the in:title qualifier.
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Restrict your search to the title by using the in:title qualifier.
Issue search results · GitHub