Vsevolod Stakhov

Yes, that looks like rust meta-hints. Hashtag symbol is not used in ucl, so there's no problem, in principle.

Hello, have you specified c99 standard for your compiler?

I can reply only the same as for issue #61: Unfortunately, I have no windows machine available for testing and I'm not very experienced in windows development tools. However, if...

In fact, I always use autotools to build libucl. I'll check plain Makefile and fix it if possible.

As far as I see from your backtrace, your `struct ucl_parser *` pointer has different values: ``` ucl_state_machine(parser=0x0000000100200000) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ucl_parser_register_variable(parser=0x00007fff5fbfdaf0, var=0x00007fff5fbfd8d0, ... ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ``` Obviously, it is not correct.

If you use C++, then you always need `reinterpret_cast` to `void *` to interact with C. This is the most ugly requirement, but it comes from C not from C++.

C style cast works exactly the same as C++ `reinterpret_cast`, however, it breaks C++ types interface and `auto` in particular, hence I'd not recommend to use C style casts in...

Unfortunately, I have no windows machine available for testing and I'm not very experienced in windows development tools. However, if you have a tested patch I'll be happy to review...

Your patch seems to be fine and I have merged it, thank you! It is also interesting whether is it possible to compile libucl with the recent msvc compiler (in...

I had no time to look deeply inside this validation language. At the first glance it looks complicated and uses xml for description. Are there any features that are supported...