Re: improved message

[Jeffrey A Law <law at cygnus dot com>]

  > I'd rather leave that to Jeff or someone else more aware of issues
  > like how it might affect the testsuite.  Either version is fine by
  > me, by the way.
Well, I'd like to settle down from constantly changing the diagnostics
from the compiler.  Every time we change it, we run the risk of screwing
ourselves or someone else that has code to parse the compiler's output.


  > >What about one other suggestion in my original message that the link
  > >in http://egcs.cygnus.com/faq.html#bugreport that points to the bug
  > >report section in the egcs manual could actualy point there the same way
  > >http://egcs.cygnus.com/onlinedocs/g77_bugs.html does. 
  > >Probably there is some wizardry involved in generating the html files
  > >from the texi documents so the name of the file containing the bugs
  > >sections stays the same. I presume you were involved in doing it for g77, 
  > could you do it in this case too? 
  > 
  > I didn't do the WWW setup for g77, I think Jeff did.  Yes, it'd be
  > nice if the same kind of "direct pointing" was done for gcc, et al.
It's in the plan to do the same for gcc.  I was kind of holding off with
the direct link in the hope that I could get the first stage of the
manual reorg done for this release.  For obscure technical reasons the code
to make the direct link is somewhat fragile and will probably break when
we start ripping apart the manual.

  > One concern I have: maybe it'd reduce confusion if the bug-reporting
  > diagnostic, as well as the installation documentation, throughout egcs --
  > basically anything with a URL to the EGCS site -- include, in the URL,
  > the version number of EGCS (GCC) somehow.
Not a bad idea.

jeff