Vsevolod Stakhov

> why not simply change libucl to return the object as an array when that happens? libucl has a parser flag to do that: `UCL_PARSER_NO_IMPLICIT_ARRAYS`

No, there isn't.

(Shrugs) By reading the docs apparently.

Yes, that might probably be used. Who volounteers to adopt it?

I'm not quite sure that this particular assertion should be removed. Assertions are used to prevent library misusage. A missing parser object is definitely an example of misusage. Assertions on...

Yes, assuming that `len == 0` implies zero terminated string was a mistake. However, I'd prefer the second option as it will not break the existing API and its usage....

The port seems to be updated, thank you @koobs!

Don't [multiline strings](https://github.com/vstakhov/libucl#multiline-strings) do the job? Or do you mean something else?

Yes, I think that is possible. I'll check later.

For your example ucl should now produce the following json: ``` json { "section": [ { "foo": { "bar": { "key": "value" } } }, { "foo": { "baz": {...