Commit 0b1eb4a9 authored by Robert P. Goldman's avatar Robert P. Goldman
Browse files

\ddo abbreviation for defsystem-depends-on to allow me to fix the hyphenation....

\ddo abbreviation for defsystem-depends-on to allow me to fix the hyphenation.  Possibly I could have done this without...
parent 27b9196c
......@@ -35,6 +35,7 @@
\newcommand{\traverse}{\lisp{tra\-verse}}
\newcommand{\perform}{\lisp{perform}}
\newcommand{\defsystem}{\lisp{defsystem}}
\newcommand{\ddo}{\lisp{:def\-sys\-tem-dep\-ends-on}}
% ASDF classes
\newcommand{\component}{\lisp{component}}
\newcommand{\operation}{\lisp{operation}}
......@@ -1294,15 +1295,15 @@ must put something like
or define their own classes and methods in the \file{.asd} file.
The problem with this is, of course, that after it
all bets are off about the readability of the file's contents.
In {\ASDFii} we extended {\defsystem} with a \lisp{:defsystem-depends-on} argument
In {\ASDFii} we extended {\defsystem} with a {\ddo} argument
so developers may declare dependencies required
\emph{in order to process the system definition}.
However, \lisp{:defsystem-depends-on} hasn't been widely adopted yet, and interacts poorly with
However, {\ddo} hasn't been widely adopted yet, and interacts poorly with
previous conventions whereby symbols in extension packages
were to be used in the {\defsystem} form.
Extension package symbols cannot be used with \lisp{:defsystem-depends-on}
Extension package symbols cannot be used with {\ddo}
because the {\defsystem} form has to be read
before the \lisp{:defsystem-depends-on} argument is processed,
before the {\ddo} argument is processed,
causing the symbols to be created.
We suspect that other aspects of the {\ASDF} extension protocol
may have to be amended before {\ASDF} can be usefully considered declarative.
......
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