4 ms·I'm curious how sscanf is considered bad?by jpjuni0r 7y agoI'm curious how sscanf is considered bad?saagarjha 7y agoscanf(“%s”, …) can cause a buffer overflow.mort96 7y agoIt sucks that there's no scanf("%.*s"), where you give the buffer length as a separate argument. The fact that it's in a string literal also makes using a compile-time constant really ugly.claystu 7y agoYou can overflow buffers all sorts of ways in C.