4 ms·

I'm not particularly familiar with C // if the callback returns non-zero, parsing will stop typedef int (callback)(const char, const char*, const cha

I'm not particularly familiar with C // if the callback returns non-zero, parsing will stop typedef int (*callback)(const char*, const char*, const char*, void*); How does that typedef ensure the behaviour mentioned in the comment, or are they unrelated?

woodruffw 3y ago
It doesn’t; it’s a convention that the programmer is expected to honor. You could pass in a different function pointer instead (or something that isn’t a function pointer at all), and the behavior would be undefined.