Vsevolod Stakhov

So it cannot load schema or it cannot validate an object using this schema?

And what if you load it from the file with something like ``` lua local res,err = parser:validate(schema_file) ``` That would help me to narrow the problem.

I think the problem here is that lua ucl interaction lacks of passing ucl objects as userdata. Instead, it copies the full structure of ucl object to a lua variable...

If you pass `ucl_object_t *` to some container (e.g. object or arrray) then it automatically manages object passed. If you also want external management, then just increase refcount by using...

We've discussed that with @bapt some time ago. But we've not concluded anything. I'd say that this feature is possible to be implemented, however, in terms of optimization it is...

That is possible to do by modifying macro API to pass a pointer to the top UCL object in the parser. However, that would work merely if you define the...

After some thinking, I've found that it's possible to get a top object from the parser structure. So no API incompatibility will be applied. But I have no idea about...

Currently unknown variables are just treated as raw strings. For example, if you have the following definition: ``` key = "$TEST"; ``` Where there is no such variable `TEST` then...

I've added a common callback for variables to ucl.

You can run the whole thing in `lldb`: `lldb pkg` and then, in the lldb prompt, run the actual command `run audit -F`. After that, you should be able to...