On 15 March 2010 15:37, Robert Goldman rpgoldman@sift.info wrote:
On 3/15/10 Mar 15 -3:20 PM, Faré wrote:
(defmethod output-files :around ((op operation) (c component)) "Translate output files, unless asked not to" (values (multiple-value-bind (files fixedp) (call-next-method) (if fixedp files (mapcar #'apply-output-translations files))) t))
It has the advantage that the :AROUND method also follows the API and other functions calling OUTPUT-FILES get to know that the paths are now fixed.
Yup, that's better. I'm putting that in my local copy, to be released this week (hopefully after having a chance to look at janderson's pathname test).
Isn't this a job for
(defmethod output-files asdf:around ((op operation) (c component) ...)
?
Meh, right at the moment I was considering getting rid of asdf:around...
Right, but the programmer is likely to want to be able to have his/her own :around method on this function signature....
What about we reserve (defmethod foo :around (op c) ...) but advertise (defmethod foo :around ((op operation) (c component)) ...) as user-definable?
[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] You don't have to like everything about me, but if you don't love me the way I am, it's not me you love, only some fantasy of yours.