On 2008-02-20, at 08:03 EST, Donald Anderson wrote:
I agree with you and Henry that it will be more useful going
forward if you accept an arbitrary expression (as a string) and
return the expression that computes the dependencies for that (also
as a string). Thus, to retrofit your code to the current "pattern"
you would analyze the expression that is the second argument to
setAttribute in the current constraint functions.
Are you doing this in RingDing? I think that would be the best
place, since then we can test against the known-working test cases.
At the moment I'm in devildog, but there's nothing that's branch-
specific at this point.
As for testing, if you want me to retrofit the current code in
compiler/NodeModel.java to use this
directly, well that could be done and tested in either branch, right?
The branch doesn't matter to me - but whether I retrofit (or merely
provide
a new internal API) does...
I was just suggesting the retrofit as a testing path (and for code-
sharing). Up to you.
I'd like to have this in Ringding, so I can take advantage of it for
the work I am doing (continuing down the path of making userclasses be
class declarations).
