Documentation comments...

[Jeffrey A Law]

  In message <4.2.0.58.20000126091736.00a23e80@redshift.com>you write:
  > My comment overall is that I shouldn't have had to dig through so much 
  > documentation without finding what appears now to be an obvious point.  I 
  > can find very explicit information on peep-hole optimization and other 
  > items.  But the mundane information is harder to come by.  Next update to 
  > the documentation you might want to consider the addition of some type of 
  > primer/library refernence/etc.  Something that helps new users gain 
  > traction more quickly than now.  My 2 cents.
Thanks for the input, but this really isn't the kind of thing we want
to try and address in the GCC documentation.

This really is outside of the scope of the kind of documentation we
want to provide in GCC -- GCC is a compiler, it doesn't have any
control over what routines are in what library on your system.  Nor
do we really want to try and provide documentation for how to program
in C.  That's way outside the scope of the GCC documentation.

GCC's documentation is designed to provide 4 kinds of information

	1. How to install GCC
	2. Language extensions found in GCC
	3. Compiler options for GCC
	4. GCC developers referenve.

jeff