Content ... the one thing that the blurb lacks
You know that a blurb is going to be useless in describing a product when it contains phrases like "enables [you] to..." and zero-content words like "content".
I wondered about the press-releasy blurb and then scrolled down to the details... The "license" field explained everything.
I hate to come off as flaming someone who has obviously spent a great deal of time putting together software for others, but this library seems to me like a combination of hash management and the rudiments of a state machine. Am I missing something?
It has become fashionable to create your own "programming paradigm", but it would be nice if those who do so would come up with more than just a new way of stringing together old libraries.
This model, for example can easily be followed to the logical conclusion of being an expert system. While that model of programming may have fallen out of favor, I think it would be good for the author to look over languages such as CLIPS and Prolog and systems such as make before continuing with a half-way effort at re-implementing some of their features.