Thanks. I'll add that. I just didn't want to duplicate code if there was already a method that did what I wanted
Sent from my iPhone
On Jun 29, 2017, at 18:34, Faré fahree@gmail.com wrote:
On Thu, Jun 29, 2017 at 7:28 PM, Robert Goldman rpgoldman@sift.net wrote: What seems like the obvious solution to this problem is to invoke RECORD-DEPENDENCY (with PLAN as NIL), but I'm afraid it's not entirely clear how to use this function. This is the DEFGENERIC:
(defgeneric record-dependency (plan operation component) (:documentation "Record an action as a dependency in the current plan"))
So the action is the (OPERATION . COMPONENT) pair. But in that case what do you mean by "record as a dependency"? I think of a dependency as a relationship between two actions, as in "in order to perform the foo operation on bar, you must perform the bletch operation on baz." But this has only one action as argument. So is this the depended on action or the dependent action? I presume the former, but if so, what is the dependent action?
It looks like you need some RECORD-INPUT-FILE function analog to RECORD-DEPENDENCY, that will inform ASDF that the action being performed has some additional input file that wasn't otherwise previously declared.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org In a five year period we can get one superb programming language. Only we can't control when the five year period will begin. — Alan Perlis