NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
several minutes ago. We don't need no stinkin' tactical nukes.
(By the way, do you have change for 10 million people?) --lwall
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Alternative futures? (Score:1)
Still, I don't think that quite solves the problem if you assert a fact and your query fails, you probably want to retract that fact.
This feels to me like you want an 'alternative futures' model of time: that is, when you backtrack, you not only go back to a previous 'time' but also arrange things so that when you go 'forward' again you are moving forward on a different timeline that diverges from the first at the point the backtrack went back to. If you change something and don't backtrack, subsequent c
Re: (Score:2)
I've no intention of simulating the many-worlds hypothesis [wikipedia.org] in Prolog, thank you ;)
I'll leave that to Damian.
Re: (Score:1)
If git can do it so can you.
Relational Databases... (Score:1)
have been wrestling with these sort of concurrency issues for decades now (and of course you can view the DB as a set of assertions). With something like mvcc you're not even dealing with a single timeline any more.
There's been a recent discussion on the pgsql-hackers list wrt some issues of implementing true serializable transactions that might feed in to
Sad how age affects you... (Score:1)
I was going to post some useful references coz I spent a large chunk of time with my undergraduate project implementing a temporal reasoning system based around a constraint propagation mechanism, intending it to form the backbone of a multi-agent planner.
Then I realised that was eighteen years ago and I cannot remember anything about the bugger - beyond the fact that it was annoyingly NP-complete and ran far too slowly to do anything useful.
Sorry!