lispdoc - results for component

component
	Mentioned in: HyperSpec - 19.2.1.1 The Pathname Host Component HyperSpec - 19.2.1.2 The Pathname Device Component HyperSpec - 19.2.1.3 The Pathname Directory Component HyperSpec - 19.2.1.4 The Pathname Name Component HyperSpec - 19.2.1.5 The Pathname Type Component HyperSpec - 19.2.1.6 The Pathname Version Component HyperSpec - 19.2.2 Interpreting Pathname Component Values HyperSpec - 19.2.2.1 Strings in Component Values HyperSpec - 19.2.2.2 Special Pathname Component Values HyperSpec - 19.2.2.2.1 NIL as a Component Value HyperSpec - 19.2.2.2.2 :WILD as a Component Value HyperSpec - 19.2.2.2.3 :UNSPECIFIC as a Component Value HyperSpec - 19.2.2.2.3.1 Relation between component values NIL and :UNSPECIFIC HyperSpec - 19.2.2.4.1 Restrictions on Examining a Pathname Host Component HyperSpec - 19.2.2.4.2 Restrictions on Examining a Pathname Device Component HyperSpec - 19.2.2.4.3 Restrictions on Examining a Pathname Directory Component HyperSpec - 19.2.2.4.4 Restrictions on Examining a Pathname Name Component HyperSpec - 19.2.2.4.5 Restrictions on Examining a Pathname Type Component HyperSpec - 19.2.2.4.6 Restrictions on Examining a Pathname Version Component HyperSpec - 19.2.2.4.7 Notes about the Pathname Version Component

components
	Mentioned in: HyperSpec - 19.2.1 Pathname Components HyperSpec - 19.2.2.1.1 Special Characters in Pathname Components HyperSpec - 19.2.2.1.2 Case in Pathname Components HyperSpec - 19.2.2.1.2.1 Local Case in Pathname Components HyperSpec - 19.2.2.1.2.2 Common Case in Pathname Components HyperSpec - 19.2.2.4 Restrictions on Examining Pathname Components HyperSpec - 19.2.2.4.3.1 Directory Components in Non-Hierarchical File Systems HyperSpec - 19.3.2 Logical Pathname Components HyperSpec - 19.3.2.1 Unspecific Components of a Logical Pathname HyperSpec - 19.3.2.2 Null Strings as Components of a Logical Pathname

asdf:component	Undocumented


(asdf:component-name object)	Undocumented


(asdf:find-component base path)	Function: Finds the component with PATH starting from BASE module; if BASE is nil, then the component is assumed to be a system.


(asdf:error-component condition)	Undocumented


(asdf:component-system component)	Function: Find the top-level system containing COMPONENT


(asdf:component-parent object)	Undocumented


(asdf:module-components object)	Undocumented


asdf:missing-component	Undocumented


(asdf:component-version object)	Undocumented


(asdf:component-pathname component)	Function: Extracts the pathname applicable for a particular component.


(asdf:component-property component property)	Undocumented


(asdf:component-visited-p operation component)	Function: Returns the value stored by a call to VISIT-COMPONENT, if that has been called, otherwise NIL. This value stored will be a cons cell, the first element of which is a computed key, so not interesting. The CDR wil be the DATA value stored by VISIT-COMPONENT; recover it as (cdr (component-visited-p op c)). In the current form of ASDF, the DATA value retrieved is effectively a boolean, indicating whether some operations are to be performed in order to do OPERATION X COMPONENT. If the data value is NIL, the combination had been explored, but no operations needed to be performed.


(asdf:component-depends-on operation component)	Function: Returns a list of dependencies needed by the component to perform the operation. A dependency has one of the following forms: (<operation> <component>), where <operation> is a class designator and each <component> is a component designator, which means that the component depends on <operation> having been performed on each <component>; or (FEATURE <feature>), which means that the component depends on <feature>'s presence in FEATURES*. Methods specialized on subclasses of existing component types should usually append the results of CALL-NEXT-METHOD to the list.


(asdf:component-relative-pathname component)	Function: Returns a pathname for the component argument intended to be interpreted relative to the pathname of that component's parent. Despite the function's name, the return value may be an absolute pathname, because an absolute pathname may be interpreted relative to another pathname in a degenerate way.


(asdf:module-components-by-name object)	Undocumented


asdf:missing-component-of-version	Undocumented


(asdf:component-name-to-pathname-components s &key force-directory force-relative)	Function: Splits the path string S, returning three values: A flag that is either :absolute or :relative, indicating how the rest of the values are to be interpreted. A directory path --- a list of strings, suitable for use with MAKE-PATHNAME when prepended with the flag value. A filename with type extension, possibly NIL in the case of a directory pathname. FORCE-DIRECTORY forces S to be interpreted as a directory pathname (third return value will be NIL, final component of S will be treated as part of the directory path. The intention of this function is to support structured component names, e.g., (:file "foo/bar"), which will be unpacked to relative pathnames.