Re: [PATCH 1/3] git-branch: add --track and --no-track options

Paolo Bonzini [off-list ref] 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).