On Wed, 16 Feb 2005 12:17:35 +1100, [EMAIL PROTECTED] (Damian Conway) wrote: > > ..values tells you what raw values are inside the junction. The other kind of > introspection that's desirable is: "what raw values can *match* this > junction". There would probably be a .states method for that. > > To see the difference between the two, consider: > > my $ideal_partner = all( any(«tall dark rich»), > any(«rich old frail»), > any(«Australian rich»), > ); > > $ideal_partner.values would return the three distinct values in the junction: > > ( any(«tall dark rich»), > any(«rich old frail»), > any(«Australian rich»), > ); > > But $ideal_partner.states would return only those non-junctive values that > (smart-)match the junction. Namely, "rich". > > >
I, and I think many others, have been trying to follow along on the discussions regarding junctions, and I have to say that for the most part, much of it goes <<insert graphic of open hand, palm down, waving to and fro above head>>. Any chance that you could provide one or two simple but realistic examples of using Junctions and their operators? I see individual snippets of use and they appear to make sense, but when I try envisage using them in code I have recently written, I find nothing leaping off the page at me as an obvious candidate. Thanks.
