Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
A
asdf
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Jan Moringen
asdf
Commits
b918e3af
Commit
b918e3af
authored
15 years ago
by
Francois-Rene Rideau
Browse files
Options
Downloads
Patches
Plain Diff
Clarify documentation a bit. This should be moved from FAQ to specification. Sigh.
parent
1a0e6645
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
asdf.texinfo
+13
-8
13 additions, 8 deletions
asdf.texinfo
with
13 additions
and
8 deletions
asdf.texinfo
+
13
−
8
View file @
b918e3af
...
@@ -1436,21 +1436,26 @@ in the spatial-trees ASDF system definition:
...
@@ -1436,21 +1436,26 @@ in the spatial-trees ASDF system definition:
(:static-file "TODO")))
(:static-file "TODO")))
@end example
@end example
All of the files in the @code
{
tree-impls
}
module are at the top level,
instead of in a @code
{
tree-impls/
}
subdirectory.
Note that the argument to @code
{
:pathname
}
can be either a pathname object or a string.
Note that the argument to @code
{
:pathname
}
can be either a pathname object or a string.
A pathname object can be constructed with the @code
{
#p"foo/bar/"
}
syntax,
A pathname object can be constructed with the @code
{
#p"foo/bar/"
}
syntax,
but this is discouraged because the results are not portable.
but this is discouraged because the results
of parsing a namestring
are not portable.
It
can only be portably constructed with such syntax as
A pathname
can only be portably constructed with such syntax as
@code
{
#.(make-pathname :directory '(:relative "foo" "bar"))
}
,
@code
{
#.(make-pathname :directory '(:relative "foo" "bar"))
}
,
and similarly the current directory can only be portably specified as
and similarly the current directory can only be portably specified as
@code
{
#.(make-pathname :directory '(:relative
"foo" "bar"
))
}
.
@code
{
#.(make-pathname :directory '(:relative))
}
.
A
s of ASDF 1.62
3, however
, you can portably use a string
,
However, a
s of ASDF 1.62
4
, you can portably use a string
to denote a pathname.
which
will be parsed as a @code
{
/
}
-separated path from the current directory,
The string
will be parsed as a @code
{
/
}
-separated path from the current directory,
such that the empty string @code
{
""
}
denotes the current directory, and
such that the empty string @code
{
""
}
denotes the current directory, and
@code
{
"foo/bar"
}
(no trailing @code
{
/
}
required in the case of modules)
@code
{
"foo/bar"
}
(no trailing @code
{
/
}
required in the case of modules)
portably denotes the same subdirectory as above.
portably denotes the same subdirectory as above.
When files are specified, the last @code
{
/
}
-separated component is interpreted
All of the files in the @code
{
tree-impls
}
module are at the top level,
either as the name component of a pathname
instead of in a @code
{
tree-impls/
}
subdirectory.
(if the component class specifies a pathname type),
or as a name component plus optional dot-separated type component
(if the component class doesn't specifies a pathname type).
@end itemize
@end itemize
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment