delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1999/07/27/09:44:38

Sender: "Rolf Campbell" <cp1v45 AT nortelnetworks DOT com>
Message-ID: <379DB712.776B7368@americasm01.nt.com>
Date: Tue, 27 Jul 1999 09:41:38 -0400
From: "Rolf Campbell" <cp1v45 AT nortelnetworks DOT com>
Organization: Nortel Networks
X-Mailer: Mozilla 4.6 [en] (X11; I; HP-UX B.10.20 9000/712)
X-Accept-Language: en
MIME-Version: 1.0
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
CC: djgpp AT delorie DOT com
Subject: Re: Strange localtime function behaviour
References: <Pine DOT SUN DOT 3 DOT 91 DOT 990727093718 DOT 5354D-100000 AT is>
Reply-To: djgpp AT delorie DOT com

Eli Zaretskii wrote:

> On Mon, 26 Jul 1999, Rolf Campbell wrote:
> > > What else would you like to see in the docs of every function?
> >     The documentation of each function is fine, but I might like to see
> > documentation for keywords like "for", "while", "#include", "#pragma", all of the
> > operators (and their precedence)
> You are talking about docs for a language, not for a library.  A library
> docs is not supposed to document the language.

    I wasn't planning on updating libc.info (or whatever the real name is).  I was
planning on making something like c.info or c++.info which would contain documentation
on the language itself.

> > and better iostream/fstream documentation (non
> > hierarchical).  And I don't think I've ever seen good documentation of "iomanip.h"
> > or some other C++ includes.
> The C++ headers and the libraries are not developed by DJGPP, they are
> ported GNU software.  If you have suggestions for improvements in the GNU
> libstdc++ libraries, please submit them to the libstdc++ maintainers.

    Are they the ones that take care of the info files as well?

--
     -Rolf Campbell (39)3-6318



- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019