Some boring questions, concluding with linear logic.
-- The embodiment code uses combo... will this continue, or is this eventually being replace by scheme (as hinted in earlier emails)?
-- The embodiment code uses a combo evaluator that performs "variable unification" However, in the combo code base, this code is marked obsolete, and is slated for removal ... so again, is this code eventually going away? Being re-written?
-- There are 4 embodiment test cases failing. As far as I can tell, its because someone moved/removed a script to autogenerate the scheme bindings for the various embodiemnt-specific atoms. Anyone working on fixing this, or is this code going obsolescent?
-- Combo seems to have all sorts of extensions for actions and perceptions in it, for use by the embodiment code. Given the above questions, do these continue to live on, or are these somehow obsoleted?
-- If they do live on, is there a particular theory of logic that applies to them? by "theory of logic", I'm thinking of a system such as some form of "constraint logic programming", or some kind of planning logic (e.g. "can't walk through doorway until door has been opened").
-- Does PLN have some kind of constraint-programming-like subsystem defined in it? i.e. for solving planning problems?
-- I've recently been reading about "linear logic", a kind of crisp logic, generalizing the usual propositional & predicate logic and "symmetrizing" sequent calculus. It has a natural embedding of constraint-type declarations, e.g. "with one dollar you can buy one apple or one candy bar but not both" and have been wondering if it might provide a better foundation for learning any kind of action/perception stuff within combo/moses. Maybe. or maybe not. I dunno.
Linas