Zachary Kessin

I think we should view the function interface as a low level building block, which may be best used to create other more specific ways of interacting with erlog. On...

It is a clunky interface, but it has the advantage of being able to be easily embeded in something else. I don't plan to use it directly but to use...

I think the idea is that we will create several high level interfaces that can serve different uses. I would not want to use the function interface directly at the...

I use get_db and set_db in the erlog-server code I am working on. I create an erlog instance load some stuff into it and then export the DB and actually...

I like @rvirding 's comments above. I can see arguments where ErlogState could be a PID or an Immutable data structure. The question is do we want to make it...

Why not use dict? it would seem an ideal pure functional data structure if you want to export it, esp if you want to embed that data in a larger...

I like the return `error` plan.

I am going to merge this into my testing branch to make everything pass (today or tomorrow if I have time) I was planning to add some IO predicates to...

Fixing the tests was pretty easy, it was mostly just refactor to the New API, none of them look at the internals

I think the question is do we want erlog to be more like SWI Prolog, or ISO Prolog, my gut says SWI, but I think its up for debate