Skip to content
GitLab
Menu
Projects
Groups
Snippets
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
asdf
asdf
Commits
2ee61c15
Commit
2ee61c15
authored
Oct 22, 2010
by
Francois-Rene Rideau
Browse files
whitespace changes
parent
14bd98c3
Changes
1
Hide whitespace changes
Inline
Side-by-side
doc/asdf.texinfo
View file @
2ee61c15
...
...
@@ -772,7 +772,7 @@ has the effect of
@end lisp
where @code
{
...
}
is the component in question.
In this case @code
{
...
}
would expand to something like
In this case @code
{
...
}
would expand to something like
@lisp
(find-component (find-system "foo") "mod")
...
...
@@ -808,9 +808,9 @@ system-option := :defsystem-depends-on system-list
module-option := :components component-list
| :serial [ t | nil ]
| :if-component-dep-fails component-dep-fail-option
| :if-component-dep-fails component-dep-fail-option
option :=
option :=
| :pathname pathname-specifier
| :default-component-class class-name
| :perform method-form
...
...
@@ -944,7 +944,7 @@ Unhappily, ASDF 1 didn't properly support
parsing component names as strings specifying paths with directories,
and the cumbersome @code
{
#.(make-pathname ...)
}
syntax had to be used.
Note that when specifying pathname objects,
Note that when specifying pathname objects,
ASDF does not do any special interpretation of the pathname
influenced by the component type, unlike the procedure for
pathname-specifying strings.
...
...
@@ -956,7 +956,7 @@ be forced upon you if you were specifying a string.
@subsection Warning about logical pathnames
@cindex logical pathnames
@cindex logical pathnames
We recommend that you not use logical pathnames
in your asdf system definitions at this point,
...
...
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