viterbi: first unit test.
more viterbi unit testing
viterbi: convert lg exps to atoms
plug a memory leak
LG AndLink must be an ordered link
start work on connector sets.
guile: explicitly check that object is a handle

Because if we just assume it is, we will crash. And that's unhappy.
OK, get back to a working unit test.

Instead of a crashing one.
Load the NLP types without spewing errors

The shared object constructors and destructors do not seem to get
called if nothing in the shared object is ever referenced. This means
the atom types don't actually get loaded.  Work around this by
creating a module; when the module is loaded, then the types get loaded.
iAdd some explanation for the previous commit
If atom type is not explicit, assume its a link.

Its kind of a hack, but I don't know what else to do.  I want to break
out of the long-name convention, its very verbose..
SchemeEval: add some candy.

Allos functions to take stringstream, not just string, for ease-of-use.
Continue with viteribi initialization sequence
Avoid usig C++ for the atomspace manipulations
misc minor cleanup
Another viterbi baby-step
Start wwriting the first parse rule...
OK, first rule is actually evaluating now
Provide types for the variables
Use cog-bind instead of the pattern matcher