Christophe Coustet

Results 8 comments of Christophe Coustet

Hello. Just a few words to say that this feature would be useful to me. I understand that writing tests is a huge amount of work, but it is too...

Hi Michael. All these features sound great! I'm currently interested in unions and validation callbacks, but others could be interesting in other projects. Is there already a release timeframe for...

I don't know if you are interested in suggestions (that is additional work), but I would found very useful to have custom log messages (through callbacks?), including verbose success reporting....

Another feature I would like is to be able to (optionally) store the parsing context of a value. Could be limited to line+column and a pointer to the parent item,...

Hi! As I see that these topics are discussed, I give my feelings again. Default values could be solved easily if a set/unset information is added: if the field hasn't...

I agree. Complex validation can only be user ad-hoc code. What I was trying to advocate is that some information is needed to output meaningful messages, like parsing context (e.g....

The idea behind the context thing is to allow to create meaningful messages from the post-parsing validation step. It has nothing to do with the per-field validation process from within...

The parser fails parsing this one too: void *\* ptr = new void *;