re PR libstdc++/59699 (Effective C++ has moved)

	PR libstdc++/59699
	* doc/xml/manual/support.xml (std.support.types.null): Update links.

From-SVN: r206526

libstdc++-v3/ChangeLog

@@ -11,6 +11,9 @@
 	* doc/xml/manual/backwards_compatibility.xml
 	(backwards.third.nocreate_noreplace): Correct and expand.
 
+	PR libstdc++/59699
+	* doc/xml/manual/support.xml (std.support.types.null): Update links.
+
 2014-01-09  Jonathan Wakely  <jwakely@redhat.com>
 
 	PR libstdc++/59738

libstdc++-v3/doc/xml/manual/support.xml

@@ -169,16 +169,18 @@
      <constant>NULL</constant> is always a pointer.)
     </para>
 
-    <para>In his book <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.awprofessional.com/titles/0-201-92488-9/"><emphasis>Effective
-    C++</emphasis></link>, Scott Meyers points out that the best way
+    <para>In his book <link xmlns:xlink="http://www.w3.org/1999/xlink"
+      xlink:href="http://www.aristeia.com/books.html"><emphasis>Effective
+      C++</emphasis></link>, Scott Meyers points out that the best way
     to solve this problem is to not overload on pointer-vs-integer
     types to begin with.  He also offers a way to make your own magic
     <constant>NULL</constant> that will match pointers before it
     matches integers.
     </para>
-    <para>See
-      <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.awprofessional.com/titles/0-201-31015-5/">the
-      Effective C++ CD example</link>
+    <para>See the
+      <link xmlns:xlink="http://www.w3.org/1999/xlink"
+      xlink:href="http://www.aristeia.com/books.html"><emphasis>Effective
+      C++ CD</emphasis></link> example.
     </para>
   </section>