mesa/src/compiler/glsl/glcpp
Dylan Baker fbf192a67e meson: Use consistent style
Currently the meosn build has a mix of two styles:
arg : [foo, ...
       bar],

and
arg : [
  foo, ...,
  bar,
]

For consistency let's pick one. I've picked the later style, which I
think is more readable, and is more common in the mesa code base.

v2: - fix commit message

Acked-by: Eric Engestrom <eric.engestrom@imgtec.com>
Signed-off-by: Dylan Baker <dylan.c.baker@intel.com>
2018-01-11 15:40:02 -08:00
..
tests Fix glcpp test expectations 2017-06-08 09:46:36 +02:00
.gitignore
glcpp-lex.l glcpp: Avoid unnecessary call to strlen 2017-09-26 18:25:38 +02:00
glcpp-parse.y glsl: Change the parser to use the string buffer 2017-09-26 18:25:00 +02:00
glcpp.c glsl: reuse main extension table to appropriately restrict extensions 2016-07-23 13:48:04 -04:00
glcpp.h glsl: Change the parser to use the string buffer 2017-09-26 18:25:00 +02:00
meson.build meson: Use consistent style 2018-01-11 15:40:02 -08:00
pp.c glcpp: Use string_buffer for line continuation removal 2017-09-26 18:25:20 +02: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).