Path

Uniquely describes the location of a test within a test hierarchy. Node order is from test case to root.

Unlabeled path

A collection of FFI declarations for interfacing with Win32.

A collection of FFI declarations for interfacing with Win32.

A collection of FFI declarations for interfacing with Win32.

This module provides various helpful utilities for dealing with path and file names, directories, and related support. Written by John Goerzen, jgoerzen@complete.org

Path of some base and type. The type variables are:

• b — base, the base location of the path; absolute or relative.
• t — type, whether file or directory.

Internally it is a PosixPath, which can be of two formats only:

1. File format: file.txt, foo/bar.txt, /foo/bar.txt
2. Directory format: foo/, /foo/bar/

All directories end in a trailing separator. There are no duplicate path separators //, no .., no ./, no ~/, etc.

Path of some base and type. The type variables are:

• b — base, the base location of the path; absolute or relative.
• t — type, whether file or directory.

Internally it is a WindowsPath, which can be of two formats only:

1. File format: file.txt, foo/bar.txt, /foo/bar.txt
2. Directory format: foo/, /foo/bar/

All directories end in a trailing separator. There are no duplicate path separators //, no .., no ./, no ~/, etc.

Path of some base and type. The type variables are:

• b — base, the base location of the path; absolute or relative.
• t — type, whether file or directory.

Internally it is a PosixPath, which can be of two formats only:

1. File format: file.txt, foo/bar.txt, /foo/bar.txt
2. Directory format: foo/, /foo/bar/

All directories end in a trailing separator. There are no duplicate path separators //, no .., no ./, no ~/, etc.

Path of some base and type. The type variables are:

• b — base, the base location of the path; absolute or relative.
• t — type, whether file or directory.

Internally it is a WindowsPath, which can be of two formats only:

1. File format: file.txt, foo/bar.txt, /foo/bar.txt
2. Directory format: foo/, /foo/bar/

All directories end in a trailing separator. There are no duplicate path separators //, no .., no ./, no ~/, etc.

This library provides a well-typed representation of paths in a filesystem directory tree. Both Path.Posix and Path.Windows provide the same interface. This module will reexport the appropriate module for your platform.

Path of some base and type. The type variables are:

• b — base, the base location of the path; absolute or relative.
• t — type, whether file or directory.

Internally is a string. The string can be of two formats only:

1. File format: file.txt, foo/bar.txt, /foo/bar.txt
2. Directory format: foo/, /foo/bar/

All directories end in a trailing separator. There are no duplicate path separators //, no .., no ./, no ~/, etc.

Path of some base and type. The type variables are:

• b — base, the base location of the path; absolute or relative.
• t — type, whether file or directory.

Internally is a string. The string can be of two formats only:

1. File format: file.txt, foo/bar.txt, /foo/bar.txt
2. Directory format: foo/, /foo/bar/

All directories end in a trailing separator. There are no duplicate path separators //, no .., no ./, no ~/, etc.

A Path describes the location of a spec item within a spec tree. It consists of a list of group descriptions and a requirement description.

High‐level, byte‐based file and directory path manipulations. You probably want to import Filesystem.Path.CurrentOS instead, since it handles detecting which rules to use in the current compilation.

A Cairo path.

• A path is a sequence of drawing operations that are accumulated until stroke is called. Using a path is particularly useful when drawing lines with special join styles and closePath.

A path is a (possibly empty) list of Located Trails. Hence, unlike trails, paths are not translationally invariant, and they form a monoid under superposition (placing one path on top of another) rather than concatenation.

This module defines paths, which are collections of concretely located Trails. Many drawing systems (cairo, svg, ...) have a similar notion of "path". Note that paths with multiple trails are necessary for being able to draw e.g. filled objects with holes in them.