Re: CVS commit: src/lib/libc/stdio

[Robert Elz <kre%munnari.OZ.AU@localhost>]

    Date:        Fri, 30 Apr 2010 06:00:14 +0000
    From:        Jukka Ruohonen <jruoho%NetBSD.org@localhost>
    Message-ID:  <20100430060014.77391175DD%cvs.netbsd.org@localhost>

  | Module Name:        src
  | Committed By:       jruoho
  | Date:               Fri Apr 30 06:00:14 UTC 2010
  | 
  | Modified Files:
  |     src/lib/libc/stdio: fgets.3
  | 
  | Log Message:
  | They've finally made gets(3) obsolete (in POSIX, at least).

I don't understand the change - that is, I don't understand the
sentence that was added to the man page, it says ...

"The revision marked gets() as obsolete..."

What revision???

The previous sentence just says that gets() (and fgets()) confirms with
specific ANSI (C) and IEEE (Posix) standards.

What's there now is just plain confusing.

While I'm here, I would also note that it really makes no sense go racing
about documenting things as not complying to some standard or other
(by which I mean, that some function is not (or no longer) a standard
function, as distinct from "our implementation is different from the
standard", which is definitely worthy of documentation.)

We have LOTS of functions that aren't standardised anywhere, racing
around saying they're not, helps no-one.

By all means document functions which do (or are intended to) conform to
some standard, and perhaps later remove that mention if the version of
the standard in question is obsolete, and newer versions don't include
the function in question (or where it is deprecated in them) - but there's
no need to include specific text saying that a function is not standard.
Simply not saying that it does conform to some standard should be enough.

kre