mesa/src/glsl/glcpp
Sir Anthony 6e39a8f6ec glcpp: Do not remove spaces to preserve locations.
After preprocessing by glcpp all adjacent spaces were replaced by
single one and glsl parser received column-shifted shader source.
It negatively affected ast location set up and produced wrong error
messages for heavily-spaced shaders.

Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>
2014-03-08 01:38:32 -08:00
..
tests glcpp: Do not remove spaces to preserve locations. 2014-03-08 01:38:32 -08:00
.gitignore glcpp: Add back tests/*.out to .gitignore 2013-01-11 11:49:33 +01:00
glcpp-lex.l glcpp: Do not remove spaces to preserve locations. 2014-03-08 01:38:32 -08:00
glcpp-parse.y glsl/sso: Add parser and AST-to-HIR support for separate shader object layouts 2014-02-21 15:41:02 -08:00
glcpp.c glcpp: Rename the variable used to enable debugging. 2014-01-31 10:02:58 -08:00
glcpp.h glcpp: Resolve implicit GLSL version to 100 if the API is ES. 2014-01-27 21:15:35 -08:00
pp.c glcpp: Resolve implicit GLSL version to 100 if the API is ES. 2014-01-27 21:15:35 -08:00
README glcpp: Update README for new support of __LINE__ and __FILE__. 2012-11-29 13:03:02 -08:00

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).