[asdf-devel] Cache? Translations? How to get rid of them?
Faré
fahree at gmail.com
Mon Mar 15 15:47:34 UTC 2010
Dear Juanjo,
> Indeed. This or any other way that does not break current ASDF. What I would
> like is seamless integration without imposing something that is prone to
> break in the future. Another possibility would be for OUTPUT-FILES to return
> two values: the list and an optional second value saying "do not translate!"
> This second value will be ignored by existing functions but it may be used
> by apply-output-translations It also has the advantage that the main output
> value remains in the same format and we do not introduce a corner case that
> might break ASDF's logic.
>
Your API sounds great. What about this?
(defmethod output-files :around ((op operation) (c component))
"Translate output files, unless asked not to"
(multiple-value-bind (files fixedp) (call-next-method)
(if fixedp
files
(mapcar #'apply-output-translations files))))
If you're OK with it, I'll push it as ASDF 1.635.
[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
Faré's Second Law of Dissent: I am Right, whence it follows that
all who disagree with me are either (1) evil, (2) stupid or (3) crazy.
(The alternatives are not mutually exclusive.)
This universal law is valid for all values of "me", including "you".
More information about the asdf-devel
mailing list