delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1999/07/26/13:57:04

Date: Mon, 26 Jul 1999 19:55:03 +0200
From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Message-Id: <199907261755.TAA02922@acp3bf.physik.rwth-aachen.de>
To: djgpp AT delorie DOT com
Subject: Re: Strange localtime function behaviour
Newsgroups: comp.os.msdos.djgpp
Organization: RWTH Aachen, III. physikalisches Institut B
X-Newsreader: TIN [version 1.2 PL2]
Reply-To: djgpp AT delorie DOT com

In article <379C9D06 DOT E5A1EDF0 AT americasm01 DOT nt DOT com> you 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) 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.

Sorry, but there's not really much point in explaining the very basics
of a programming language as part of the docs of any particular
compiler. That's what reference books and textbooks are for. Like K&R2
for C, or Stroustrup (3rd ed.) for C++.

Apart from that, '#include' is documented (see the 'The GNU C
Preprocessor' in info), I think, as is #pragma.

In the case of C++ standard libs like iostreams, we rely on what the
GNU project gives us (they write the library --> they document it).

Remember: you get what you pay for, and this thing comes for free...
If you have precise ideas how to improve things, feel free to jump in
and help.

--
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -


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