Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
A
asdf
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
16
Issues
16
List
Boards
Labels
Service Desk
Milestones
Merge Requests
8
Merge Requests
8
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Operations
Operations
Incidents
Environments
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
asdf
asdf
Commits
4a290576
Commit
4a290576
authored
Mar 17, 2011
by
Francois-Rene Rideau
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Clarify (hopefully) the spec for system-relative-pathname, for lp#737081
parent
7c2984bb
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
10 additions
and
9 deletions
+10
-9
doc/asdf.texinfo
doc/asdf.texinfo
+10
-9
No files found.
doc/asdf.texinfo
View file @
4a290576
...
...
@@ -2706,20 +2706,21 @@ useful for system definition and development. These include:
It's often handy to locate a file relative to some system.
The @code
{
system
-
relative
-
pathname
}
function meets this need.
It takes two arguments: the name of a system and a relative pathname.
It returns a pathname built from the location of the system's source file
and the relative pathname. For example
It takes two mandatory arguments @var
{
system
}
and @var
{
name
}
and a keyword argument @var
{
type
}
:
@var
{
system
}
is name of a system, whereas @var
{
name
}
and optionally @var
{
type
}
specify a relative pathname, interpreted like a component pathname specifier
by @code
{
merge
-
component
-
name
-
type
}
. @xref
{
The defsystem grammar,,Pathname specifiers
}
.
It returns a pathname built from the location of the system's
source directory and the relative pathname. For example:
@lisp
>
(
asdf:system
-
relative
-
pathname 'cl
-
ppcre
#p
"regex.data"
)
>
(
asdf:system
-
relative
-
pathname 'cl
-
ppcre "regex.data"
)
#P"
/
repository
/
other
/
cl
-
ppcre
/
regex.data"
@end lisp
Instead of a pathname, you can provide a symbol or a string,
and optionally a keyword argument @code
{
type
}
.
The arguments will then be interpreted in the same way
as pathname specifiers for components.
@xref
{
The defsystem grammar,,Pathname specifiers
}
.
@end defun
@defun system
-
source
-
directory system
-
designator
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment