Re: lib/41894: [dM] printw return value wrong

[Brett Lymn <blymn%baesystems.com.au@localhost>]

The following reply was made to PR lib/41894; it has been noted by GNATS.

From: Brett Lymn <blymn%baesystems.com.au@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: lib-bug-people%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, 
netbsd-bugs%netbsd.org@localhost,
        mouse%Rodents-Montreal.ORG@localhost
Subject: Re: lib/41894: [dM] printw return value wrong
Date: Sun, 16 Aug 2009 14:22:22 +0930

 On Sun, Aug 16, 2009 at 04:25:01AM +0000, der Mouse wrote:
 > 
 >  In off-ticket correspnodence, someone pointed out to me that there's a
 >  RETURN VALUES section which specifies the existing return values.
 >  
 
 According to SUSv2 the return values section is correct.  The only values
 returned by printw() and friends are ERR and OK.
 
 >  So the manpage contradicts itself, and needs updating whether or not
 >  anything is done to the code - either the RETURN VALUES section needs
 >  updating or the description needs to note that the return value is not
 >  an aspect of printf's interface which is carried over to printw's.
 >  
 
 This is a doc bug - the phrase "the same as" should be changed to
 "similar to" which is a synonym for the SUSv2 wording of "analogous"
 
 >  Naturally, I'd prefer to see the printf-like behaviour, since that's
 >  the more useful, but, if SUS specifies the less informative behaviour,
 >  then this really is just ("just", heh) a doc-bug.
 >  
 
 Much as I agree witht he sentiment of the usefulness of the printf like
 behaviour SUSv2 disagrees..
 
 -- 
 Brett Lymn
 "Warning:
 The information contained in this email and any attached files is
 confidential to BAE Systems Australia. If you are not the intended
 recipient, any use, disclosure or copying of this email or any
 attachments is expressly prohibited.  If you have received this email
 in error, please notify us immediately. VIRUS: Every care has been
 taken to ensure this email and its attachments are virus free,
 however, any loss or damage incurred in using this email is not the
 sender's responsibility.  It is your responsibility to ensure virus
 checks are completed before installing any data sent in this email to
 your computer."