mesa/src/glsl/glcpp
Carl Worth a47a0200a7 Revert "glcpp: Rewrite line-continuation support to act globally."
This reverts commit 962a1c07b4.

Further testing revealed that this commit can cause the pre-processor to enter
infinite loops. For now, simply revert this code until a cleaner,
better-tested version is available.
2012-11-30 17:17:56 -08:00
..
tests glcpp: Add test involving token pasting of INTEGER tokens. 2012-11-29 13:03:02 -08:00
.gitignore automake: convert libglsl 2012-07-13 12:43:41 +01:00
glcpp-lex.l glcpp: Support #elif(expression) with no intervening space. 2012-11-28 10:27:02 -08:00
glcpp-parse.y glcpp: Add support for pasting of INTEGER tokens. 2012-11-29 13:03:02 -08:00
glcpp.c mesa: Rename API_OPENGL to API_OPENGL_COMPAT. 2012-11-29 11:33:15 -08:00
glcpp.h mesa/glsl: rename preprocess to glcpp_preprocess 2012-09-15 08:22:55 +10:00
Makefile.am glcpp: wire up glcpp-test to make check 2012-11-09 14:33:08 -08:00
pp.c Revert "glcpp: Rewrite line-continuation support to act globally." 2012-11-30 17:17:56 -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).