mesa/src/glsl/glcpp at 61cea49014df6dcf3aa41ad18b2e998e6921320f - mesa

Files

T

Carl Worth 61cea49014 glcpp: Add a more descriptive comment for the SKIP state manipulation

Two things make this code confusing:

	1. The uncharacteristic manipulation of lexer start state outside of
	   flex rules.

	2. The confusing semantics of the skip_stack (including the
	   "lexing_if" override and the SKIP_NO_SKIP state).

This new comment is intended to bring a bit more clarity for any readers.

There is no intended beahvioral change to the code here. The actual code
changes include better indentation to avoid an excessively-long line, and
using the more descriptive INITIAL rather than 0.

Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>
Reviewed-by: Ian Romanick <ian.d.romanick@intel.com>

2014-01-02 14:15:24 -08:00

tests

glcpp: Add test case for recently fixed loop-control underflow bug.

2013-06-03 13:33:32 -07:00

.gitignore

glcpp: Add back tests/*.out to .gitignore

2013-01-11 11:49:33 +01:00

glcpp-lex.l

glcpp: Add a more descriptive comment for the SKIP state manipulation

2014-01-02 14:15:24 -08:00

glcpp-parse.y

mesa: Add infrastructure for GL_ARB_sample_shading

2013-11-01 16:01:47 -07:00

glcpp.c

glcpp: Add --disable-line-continuations argument to standalone glcpp

2013-01-11 13:55:41 -08:00

glcpp.h

glcpp: Accept pointer to GL context rather than just the API version

2013-01-11 13:55:41 -08:00

pp.c

glcpp: Fix post-decrement underflow in loop-control variable

2013-06-03 13:33:31 -07:00

README

glcpp: Update README for new support of __LINE__ and __FILE__.

2012-11-29 13:03:02 -08:00

README

glcpp -- GLSL "C" preprocessor

This is a simple preprocessor designed to provide the preprocessing
needs of the GLSL language. The requirements for this preprocessor are
specified in the GLSL 1.30 specification availble from:

http://www.opengl.org/registry/doc/GLSLangSpec.Full.1.30.10.pdf

This specification is not precise on some semantics, (for example,
#define and #if), defining these merely "as is standard for C++
preprocessors". To fill in these details, I've been using a draft of
the C99 standard as available from:

http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1256.pdf

Any downstream compiler accepting output from glcpp should be prepared
to encounter and deal with the following preprocessor macros:

	#line
	#pragma
	#extension

All other macros will be handled according to the GLSL specification
and will not appear in the output.

Known limitations
-----------------
A file that ends with a function-like macro name as the last
non-whitespace token will result in a parse error, (where it should be
passed through as is).