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
ilc2010
Commits
0faca016
Commit
0faca016
authored
Aug 31, 2010
by
Francois-Rene Rideau
Browse files
Merge branch 'master' of
ssh://common-lisp.net/project/asdf/git/ilc2010
parents
58bc1037
4177e221
Changes
2
Hide whitespace changes
Inline
Side-by-side
asdf.tex
View file @
0faca016
...
...
@@ -120,10 +120,11 @@ Supporting a new file type is relatively easy with {\make},
by adding a new rule with an appropriate pattern to recognize
filenames with the conventional extension,
and corresponding shell commands.
With
{
\ASDF
}
, supporting a new file type
Supporting a new file type in
{
\ASDF
}
is more involved,
requiring one to define a class and a few methods
as extensions to the
{
\ASDF
}
protocol.
Unfortunately, this procedure is complicated by the fact that the
\ASDF
{}
protocol is poorly documented.
On the other hand, when building C programs with
{
\make
}
,
arbitrary side-effects have to be specified
...
...
main.tex
View file @
0faca016
...
...
@@ -142,7 +142,7 @@ compiling and loading, and components other than {\CL} source files and modules.
The vast majority of
{
\CL
}
libraries
are delivered with
{
\ASDF
}
system descriptions, and
assume that
{
\ASDF
}
will be present to satisfy their own library dependencies.
{
\ASDF
}
has taken that role because of the
y
way it simplifies
{
\ASDF
}
has taken that role because of the way it simplifies
not just the building and loading,
but also the installation of
{
\CL
}
libraries.
...
...
@@ -183,7 +183,7 @@ and the lessons we learned.
The social issues arose from the central role of
{
\ASDF
}
--- we were determined
not to ``break the community'' with the introduction of
{
\ASDFii
}
--- and
imposed many technical challenges. One of the most interesting technical
challenges was to develop a portable means to hot upgrade
for
{
\ASDF
}
,
challenges was to develop a portable means to hot upgrade
{
\ASDF
}
,
as discussed above.
In the immediately following section, we introduce
{
\ASDF
}
,
...
...
@@ -1067,7 +1067,7 @@ or by specializing the class of the source files in the module.
Trying to fix composite dependencies in
{
\traverse
}
, therefore,
opened a big can of worms.
The rule of good engineering that
{
\ASDF
}
fails to adhere to is,
\moneyquote
{
thou shal
l
tailor thy datastructures to the target problem
}
,
\moneyquote
{
thou shal
t
tailor thy datastructures to the target problem
}
,
not pick them based on how easy they are to express
in the underlying programming language
(and if your programming language isn't expressive enough,
...
...
@@ -1368,8 +1368,8 @@ but may be part of a future {\ASDFiii}.
% At the same time, it would be appropriate to improve introspection
% by making {\traverse} part of the {\ASDF} API.
On the other hand,
t
here have been calls to make
{
\traverse
}
part of the
{
\ASDF
}
API
T
here have been calls to make
{
\traverse
}
part of the
{
\ASDF
}
API
in order to enable more introspection.
This would be especially useful for authors of
{
\ASDF
}
extensions.
It would be wise to resolve the
{
\traverse
}
bug before doing this,
...
...
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