PATCH: Update docs

[Boehne, Robert]

Hello,

It has been some time since tags were added to Libtool,
and I've finally gotten arount to an update of the
documentation to reflect the real state of C++.

Yeah, I know it says "ChangeLog entry in plain text" but
I'm lazy today.

-- 
Robert Boehne             Software Engineer
Ricardo Software   Chicago Technical Center
TEL: (630)789-0003 x. 238
FAX: (630)789-0127
email:  address@hidden

? patches
? install-sh
? mkinstalldirs
? missing
? INSTALL
? COPYING
? load-archive.patch
? docs-update.patch
? doc-CXX.patch
? demo/hell_static
? depdemo/depdemo_static
? libltdl/config-h.in
? mdemo/mdemo_static
Index: ChangeLog
===================================================================
RCS file: /cvsroot/libtool/libtool/ChangeLog,v
retrieving revision 1.1100
diff -u -r1.1100 ChangeLog
--- ChangeLog   14 Apr 2002 21:34:04 -0000      1.1100
+++ ChangeLog   14 Apr 2002 21:59:02 -0000
@@ -1,3 +1,8 @@
+2002-04-14  Robert Boehne  <address@hidden>
+
+       * doc/libtool.texi (C++ libraries): Finally updated to reflect
+       Libtool's support for C++.
+
 2002-04-14  Jean-Frederic Clere  <address@hidden>
 
        * libtool.m4: Update support for Fujistu-Siemens Computers (FSC).
Index: doc/libtool.texi
===================================================================
RCS file: /cvsroot/libtool/libtool/doc/libtool.texi,v
retrieving revision 1.123
diff -u -r1.123 libtool.texi
--- doc/libtool.texi    27 Nov 2001 19:31:22 -0000      1.123
+++ doc/libtool.texi    14 Apr 2002 21:59:02 -0000
@@ -3571,22 +3571,14 @@
 libtool does not know which are these libraries, so it cannot even run
 the inter-library dependence analyzer to check how to link it in.
 Therefore, running @file{ld} to link a C++ program or library is deemed
-to fail.  However, running the C++ compiler directly may lead to
-problems related with inter-library dependencies.
+to fail.
 @end enumerate
 
-The conclusion is that libtool is not ready for general use for C++
-libraries.  You should avoid any global or static variable
-initializations that would cause an ``initializer element is not
-constant'' error if you compiled them with a standard C compiler.
-
-There are other ways of working around this problem, but they are beyond
-the scope of this manual.
-
-Furthermore, you'd better find out, at configure time, what are the C++
-Standard libraries that the C++ compiler will link in by default, and
-explicitly list them in the link command line.  Hopefully, in the
-future, libtool will be able to do this job by itself.
+Because of these three issues, Libtool has been designed to always use
+the C++ compiler to compile and link C++ programs and libraries.  In
+some instances the @code{main()} function of a program must also be
+compiled with the C++ compiler for static C++ objects to be properly
+initialized.
 
 
 @node Troubleshooting