hi EC,
At a meeting about a month ago when we discussed
Mantis 3003, Arturo pointed out that you can use
class methods as a way to capture constraints.
I have uploaded a short document to 3003 describing
how I've done exactly that (if I understood Arturo
correctly) in the past. It offers a way to pass
constraints around easily, using existing language
features, but does NOT help with the much trickier
problem of how to compose constraints.
There hasn't been much discussion of the constraint
composition issue thus far; it looks like a challenge
to me, and I'm tempted to suggest that we should abandon
it as being too problematic for the current short
timescales, instead putting more emphasis on coming up
with a good plan for soft/default constraints (which
I see as being a much more pressing need for users).
Thoughts?
Jonathan Bromley
-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Sun Oct 24 07:40:51 2010
This archive was generated by hypermail 2.1.8 : Sun Oct 24 2010 - 07:41:01 PDT