Lines Matching full:language
1 OpenGL(R) Shading Language Extension Conventions
21 The ARB OpenGL Shading Language working group has defined the following
23 Shading Language syntax or semantics.
29 We expect the Shading Language to continue to evolve through the
31 revisions to the core language specification itself. As a result,
34 language.
47 The fact that the Shading Language is modeled after C/C++ means
48 that we have some additional requirements for what the language
53 Shading Language.
62 shading language extensions do not conflict in syntax or
66 Rules for adding or modifying specific Shading Language
102 shading language specification already follow this
105 New variables added by shading language extensions should
126 how C/C++ handle keyword extensions. The core language
128 keyword so that future language revisions from the ARB will
151 defined by Shading Language constructs (case 1c2). Currently the
218 approves, the ARB would revise the shading language grammar
258 Since none of the standard core Shading Language functions
262 the Shading Language specifically allows user overloading of
277 shading language
283 Every extension which affects shading language semantics or
284 syntax must create a Shading Language preprocessor #define that
286 available in the shading language if and only if the extension
287 were supported on a given Shading Language implementation.
289 Further, extensions which do not affect shading language
290 semantics or syntax *must not* create this Shading Language
294 will be updated to include a placeholder for shading language
300 should also add a Shading Language preprocessor #define called
314 language syntax or behavior, they can simply query the
333 towards portability in the shading language. The concern is
343 shading language), the extension must introduce an API which
349 of the shading language, the shader author must explicitly make
368 See section 3.3 of the OpenGL Shading Language specification
369 (Language Version 1.20) for details about using this mechanism.
387 - cleaned up language about when to use 1c1 or 1c2
390 - language cleanups including removing use of "built in"
394 - change language about "decorate"ing names to "affix"