I will admit I am impressed how Google provides redirects for such
older links. And while I was at it, I tweaked the link description
from "this" to at least "this post".
Applied (revision 245565).
Gerald
2017-02-18 Gerald Pfeifer <ger...@pfeifer.com>
* doc/xml/manual/io.xml: Update link to groups.google.com.
Tweak link description.
Index: doc/xml/manual/io.xml
===================================================================
--- doc/xml/manual/io.xml (revision 245564)
+++ doc/xml/manual/io.xml (working copy)
@@ -576,8 +576,8 @@
<para>
An instructive thread from comp.lang.c++.moderated delved off into
this topic starting more or less at
- <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="http://groups.google.com/group/comp.std.c++/browse_thread/thread/f87b4abd7954a87/946a3eb9921e382d?q=comp.std.c%2B%2B+binary+iostream#946a3eb9921e382d";>this</link>
- post and continuing to the end of the thread. (The subject heading is
"binary iostreams" on both comp.std.c++
+ <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="https://groups.google.com/forum/#!topic/comp.std.c++/D4e0q9eVSoc";>this
post</link>
+ and continuing to the end of the thread. (The subject heading is "binary
iostreams" on both comp.std.c++
and comp.lang.c++.moderated.) Take special note of the replies by James
Kanze and Dietmar Kühl.
</para>
<para>Briefly, the problems of byte ordering and type sizes mean that
