Commit 9f0c175b authored by Robert P. Goldman's avatar Robert P. Goldman
Browse files

Minor tweak to discussion of extending ASDF and make --- there was redundancy...

Minor tweak to discussion of extending ASDF and make --- there was redundancy and I pointed out that the protocol is ill-defined.
parent 9967e000
...@@ -120,10 +120,11 @@ Supporting a new file type is relatively easy with {\make}, ...@@ -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 by adding a new rule with an appropriate pattern to recognize
filenames with the conventional extension, filenames with the conventional extension,
and corresponding shell commands. and corresponding shell commands.
With {\ASDF}, supporting a new file type
Supporting a new file type in {\ASDF} is more involved, Supporting a new file type in {\ASDF} is more involved,
requiring one to define a class and a few methods requiring one to define a class and a few methods
as extensions to the {\ASDF} protocol. 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}, On the other hand, when building C programs with {\make},
arbitrary side-effects have to be specified arbitrary side-effects have to be specified
......
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