Lines Matching full:path

68                                  const char *const *path,
155                                      const char * const *path,
158     <path> is an ordered array of <count> pointers to optionally
163     strings in the <path> argument are considered null-terminated.
165     Each string in <path> must be a valid <pathname> as defined in
167     begin with the character '/'. The ordered list of <path>s is used
200       - <count> is greater than zero and <path> is NULL, or any
201         of the pointers path[0] .. path[<count>-1] is NULL.
202       - Any of the strings in <path> are not valid pathnames beginning
383     string is identified by the path provided in the shader to the
402     The #include directive is followed by a quoted <path>; a string
405     #include "path"
406     #include <path>
408     This will lookup <path> in the supplied tree, as described in Appendix
412     compile-time error if <path> is not valid as described in Appendix
415     If <path> starts with a forward slash, whether it is quoted with
417     ignored and <path> is looked up in the tree as described in Appendix
418     A. It is a compile-time error if a path starting with a forward
425     If <path> does not start with a forward slash, it is a path relative
426     to one of the ordered list of initial search points. If this path is
429     subsequent search point, in order, until a matching path is found in
438       * the first time the path is found in the tree relative to a
439         search point, there is no string assigned to that path
440       * the path is not found relative to any of the search points."
446     which source string number is currently being processed, or the path
447     of the string if the string was an included string. This path will
448     be the same as the path supplied to the #include directive."
457        #line <line> "<path>"
460     expressions and <path> is a valid string for a path supplied in the
464     or <path> path. Subsequent source strings will be numbered
491     The locations in the tree are created or looked up by path strings.
492     The path string "/" locates the root of the tree. The path "/foo"
493     locates the child "foo" of the root. Formally, a valid path is a
495     path-separator forward slash ( / ), and by the end of the string.
499     two tokens; "foo" and ".bar". A path is invalid if
501       * <path> contains any characters not listed in Section 3.1
505       * <path> has consecutive forward slashes ( // ); "/foo//bar" is
507       * <path> ends with a forward slash ( / ), or
508       * <path> contains no characters.
510     There are no path escape characters, so there is no way to get the
513     When using a path to lookup a tree location, the path tokens are
516     tokens in the path. (Paths starting with "/" will start at the
537     a path is used to find a location in the tree, it is for the purpose
540     Hence, the tree can be built from a collection of (path,string)
541     pairs, where path is a string establishing the existence of a
577         <path> (Bug 9006).
622       - Pass multiple path strings to CompileShaderInclude, instead of
798         path "//usr/include/GL", which is not a valid search path in
843         as defining named strings under "/<vendorname>/path" and
855         path.