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
6646f910
Commit
6646f910
authored
14 years ago
by
Robert P. Goldman
Browse files
Options
Downloads
Patches
Plain Diff
Marginally improved the discussion in "A more involved example" [of defsystem].
parent
7b629476
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/asdf.texinfo
+35
-14
35 additions, 14 deletions
doc/asdf.texinfo
with
35 additions
and
14 deletions
doc/asdf.texinfo
+
35
−
14
View file @
6646f910
...
...
@@ -736,16 +736,24 @@ slightly convoluted example:
@lisp
(defsystem "foo"
:version "1.0"
:components ((:module "foo" :components ((:file "bar") (:file"baz")
(:file "quux"))
:perform (compile-op :after (op c)
(do-something c))
:explain (compile-op :after (op c)
(explain-something c)))
(:file "blah")))
:components ((:module "mod"
:components ((:file "bar")
(:file"baz")
(:file "quux"))
:perform (compile-op :after (op c)
(do-something c))
:explain (compile-op :after (op c)
(explain-something c)))
(:file "blah")))
@end lisp
The method-form tokens need explaining: essentially, this part:
The @code
{
:module
}
component named @code
{
"mod"
}
is a collection of three files,
which will be located in a subdirectory of the main code directory named
@file
{
mod
}
(this location can be overridden; see the discussion of the
@code
{
:pathname
}
option in @ref
{
The defsystem grammar
}
).
The method-form tokens provide a shorthand for defining methods on
particular components. This part
@lisp
:perform (compile-op :after (op c)
...
...
@@ -763,12 +771,25 @@ has the effect of
(explain-something c))
@end lisp
where @code
{
...
}
is the component in question;
note that although this also supports @code
{
:before
}
methods,
they may not do what you want them to ---
a @code
{
:before
}
method on perform @code
{
((op compile-op) (c (eql ...)))
}
will run after all the dependencies and sub-components have been processed,
but before the component in question has been compiled.
where @code
{
...
}
is the component in question.
In this case @code
{
...
}
would expand to something like
@lisp
(find-component (find-system "foo") "mod")
@end lisp
For more details on the syntax of such forms, see @ref
{
The defsystem
grammar
}
.
For more details on what these methods do, @pxref
{
Operations
}
in
@ref
{
The object model of ASDF
}
.
@c The following plunge into the weeds is not appropriate in this
@c location. [2010/10/03:rpg]
@c note that although this also supports @code
{
:before
}
methods,
@c they may not do what you want them to ---
@c a @code
{
:before
}
method on perform @code
{
((op compile-op) (c (eql ...)))
}
@c will run after all the dependencies and sub-components have been processed,
@c but before the component in question has been compiled.
@node The defsystem grammar, Other code in .asd files, A more involved example, Defining systems with defsystem
@comment node-name, next, previous, up
...
...
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