print format string on error/warning

[maddinat0r]

Like it has been written here.
Adding a whole OnError callback would be overkill though.
Hell, I could even use my log library to log that stuff (however that's probably overkill too).

[maddinat0r]

Printing the format string will very likely only help in cases where the format string is long and complicated, e. g. distinguishable/unique. Most sscanf calls are likely to have only a few format specifiers.
I'll use my log-core library for that when it's ready, as it reports at which line exactly a faulty sscanf call is.

[NexiusTailer]

I'll use my log-core library for that when it's ready, as it reports at which line exactly a faulty sscanf call is.

That exactly what is needed to do now when log-core is done. Do you still maintain this and have an opportunity to finally add this functionality of logging a specific line from pawn script on which sscanf is faced with a problem? This is still very relevant and several people asked me to create a similar issue here, but it seems you did it much earlier 😄

[Y-Less]

OnError (or OnSSCANFError is an option. The other option is the true (secret hidden) meaning of the sscanf return values. 0 has always meant "no error", but in the first pawn version of sscanf any other value returned was actually the index (+ 1) of the specifier that caused the error. I should re-introduce that feature.

I also have file and line information on errors now, so when you do get an error you can at least read more detailed information in the console on where it came from.