I see what you mean. I had the impression you wanted to embed it in pl/sql, transact-sql or similar. Yeah, the engine is completely seperate from the intended purpose. In my implementation, I created a base context that can be extended to "get stuff" from an object.

my $engine = Verify->new();
my $contex = ObjectInspectingVerifyContext->new();
context->set_object($someInput);
my $some_result = $engine->run($context);
...
...
...
[download]

I could imagine something like it could be thrown into catalyst as a plugin to validate every request.

After chatting w/ bart in this thread, I'm coming to the conclusion that the data is valid for use as content vs. if it is correct in context. I regret bringing up checking if a person is valid.

Is 1-818-287-1283 a valid phone number? Yes. Is it in use? Who knows. Is 82831 a valid zip code? Sure, because the rules for what a zip code is holds true. Is it valid within the context of the united states as a place to mail stuff, maybe not. Is someone's age, "chair"? No, impossible. I don't have to look at their birthdate and do some nasty calculations to figure it out. Assigning "chair" to "age", the content makes no sense. Assigning 50 makes sense in logical terms, just not in the context of any given person.

Checking whehter something is feasable is very easy. Whether or not it can hold true in context usually takes more work.

Maybe I'm wrong, and you can explain to me if there is no real deliniation and I'm off my rocker. Thoughts?

Update: Think deterministic vs non-deterministic programming.

P.S. I think Acid's main point was, he dislikes mini languages such as , and rather everything be in one language. I don't agree since perl is waaay too powerful (IMHO) for the intended purpose as I explained before.