Your message dated Mon, 28 Dec 2015 08:25:02 +0100 with message-id <ca+7wuszhqpqe_sr++alonxbklro6vtbvhijb5ryjwcwsdsr...@mail.gmail.com> and subject line Re: Bug#804210: Invalid documentation for return value of sscanf has caused the Debian Bug report #804210, regarding Invalid documentation for return value of sscanf to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 804210: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804210 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: manpages-dev Version: 3.74-1 Currently `man sscanf`` reads as: [...] RETURN VALUE These functions return the number of input items successfully matched and assigned, which can be fewer than provided for, or even zero in the event of an early matching failure. [...] This is incorrect in case a read failure occurs before the first receiving argument. cppreference reads as (suggested change): [...] Return value Number of receiving arguments successfully assigned, or EOF if read failure occurs before the first receiving argument was assigned. [...] ref: http://en.cppreference.com/w/cpp/io/c/fscanf example: [...] int i; int n = sscanf( "ABC", "ABCD%d", &i ); // n -> EOF [...]
--- End Message ---
--- Begin Message ---Control: tags -1 wontfix On Sun, Dec 27, 2015 at 4:01 PM, Michael Kerrisk (man-pages) <[email protected]> wrote: > On 11/06/2015 09:45 AM, Mathieu Malaterre wrote: >> Package: manpages-dev >> Version: 3.74-1 >> >> Currently `man sscanf`` reads as: >> >> [...] >> RETURN VALUE >> These functions return the number of input items successfully >> matched and assigned, which can be fewer than provided for, or even >> zero in the event of an early matching failure. >> [...] >> >> This is incorrect in case a read failure occurs before the first >> receiving argument. cppreference reads as (suggested change): >> >> [...] >> Return value >> >> Number of receiving arguments successfully assigned, or EOF if read >> failure occurs before the first receiving argument was assigned. >> [...] >> >> ref: http://en.cppreference.com/w/cpp/io/c/fscanf >> >> example: >> >> [...] >> int i; >> int n = sscanf( "ABC", "ABCD%d", &i ); // n -> EOF >> [...] > > [Upstream maintainer here] > > I'm puzzled. Isn't the information you require covered in the > very *next* paragraph of the manual page: > > The value EOF is returned if the end of input is reached before > either the first successful conversion or a matching failure > occurs. EOF is also returned if a read error occurs, in which > case the error indicator for the stream (see ferror(3)) is set, > and errno is set to indicate the error. Hi, I cant remember what I did here. Either I failed to read that section or I mixup 'early matching failure' with 'first matching failure'. Sorry for the noise.
--- End Message ---
