[v3] libstdc++/34015

[Benjamin Kosnik]

This removes the long line.

Instead, the warning line is reverted to something that makes sense as
a single string, instead of fancy ascii art. If people care about how
to fix this correctly (debatable), the replacements are still listed in
the comments. This seemed like an acceptable way around the link to
web-docs.

Only some of these backwards headers (hash_*, strstream) make sense to
warn about on a per-file basis. For the others, we have to resort to
other means, some of which are presently not working. For this reason, I
think it makes sense to have the full
list of replacement functions somewhere in backwards_warning.h, even if
it is not part of the diagnostic.

However, I intend to also add information about the compat bits to
the web docs here:
http://gcc.gnu.org/onlinedocs/libstdc++/17_intro/backwards_compatibility.html

That patch is pending.

tested x86/linux

-benjamin
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: p.20071211-1
URL: <http://gcc.gnu.org/pipermail/gcc-patches/attachments/20071211/c6fe352b/attachment.ksh>