Paolo Bonzini <paolo.bonzini@xxxxxxxxxxx> writes: > No, it's not. But it's helped a lot by using sscanf itself, > and "%n" is the only way I know to reliably test the return > code of sscanf and, in the process, save one strchr and one > strlen. Ok, let's see if that is true in the next round, then. I do not have much against sscanf(%n) as long as its return value is not depended upon (the portability issue as you mentioned). - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html