Commit 0faca016 authored by Francois-Rene Rideau's avatar Francois-Rene Rideau
Browse files
parents 58bc1037 4177e221
......@@ -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
......
......@@ -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 they 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 shall tailor thy datastructures to the target problem},
\moneyquote{thou shalt 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,
there have been calls to make {\traverse} part of the {\ASDF} API
There 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,
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment