Bug#351411: manpages-dev: sscanf updates

2006-02-05 Thread Michael Kerrisk
> sscanf manpages is much improved; thanks for that.  I note a missing
> period:
> 
>   flex To include a close bracket in the set, make  it  the  first
>  ^^^

Good spotting -- consequence of an older formatting error.
Fixed for 2.23.

> Also, you might consider adding a (third) instance of "whichever
> happens/occurs first":
> 
>   in) set or when the field width runs out.
>   , whichever happens first.

I think it isn't really needed.

> Additionally, I would like to tweak the phrasing of the return value,
> again.
> 
>The value EOF is returned if the end of input  is  reached
>before  the first  successful  conversion  or matching failure
>occurs.  EOF is also
> 
> If I understand correctly:
> 
> EOF is returned if the end of input is reached before the first
> sucessful onversion, or before a matching failure or occurs.
>
> 
> Without this word, it isn't clear that all matching failures won't
> return EOF.  This is not what happens; a matching failure results in
> returning with a value smaller than than count of requested
> assignments.

This feels nit-picky ;-).  Nevertheless, I rewrote as

EOF is returned if the end of input is reached before either 
the first sucessful onversion or a matching failure or occurs.

Cheers,

Michael

PS Please close this report.

-- 
Michael Kerrisk
maintainer of Linux man pages Sections 2, 3, 4, 5, and 7 

Want to help with man page maintenance?  
Grab the latest tarball at
ftp://ftp.win.tue.nl/pub/linux-local/manpages/, 
read the HOWTOHELP file and grep the source 
files for 'FIXME'.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#351411: manpages-dev: sscanf updates

2006-02-04 Thread Justin Pryzby
Package: manpages-dev
Version: 2.17-1
Severity: minor
Tags: upstream

sscanf manpages is much improved; thanks for that.  I note a missing
period:

  flex To include a close bracket in the set, make  it  the  first
 ^^^

Also, you might consider adding a (third) instance of "whichever
happens/occurs first":

  in) set or when the field width runs out.
  , whichever happens first.

Additionally, I would like to tweak the phrasing of the return value,
again.

   The value EOF is returned if the end of input  is  reached
   before  the first  successful  conversion  or matching failure
   occurs.  EOF is also

If I understand correctly:

EOF is returned if the end of input is reached before the first
sucessful onversion, or before a matching failure or occurs.
   

Without this word, it isn't clear that all matching failures won't
return EOF.  This is not what happens; a matching failure results in
returning with a value smaller than than count of requested
assignments.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]