* TODO: Remove item: no need for a libltdl without stdio.

diff --git a/ChangeLog b/ChangeLog
index 92ac72eb661a378b788cdd268bda0299495f7f08..dcbce38dad7f9cf5357cc042541a1ec4a0812b49 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+2004-10-07  Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
+
+       * TODO: Remove item: no need for a libltdl without stdio.
+
 2004-10-07  Gary V. Vaughan  <gary@gnu.org>
 
        * tests/defs.m4sh (scripts): Actually scan the generated ltmain.sh

diff --git a/TODO b/TODO
index b7855e204559e348376e4e429f313d1e754caffb..ef1c59fa6eecee3702c42a1078fa85f6cd664c09 100644 (file)
--- a/TODO
+++ b/TODO
@@ -137,22 +137,6 @@ GNU Libtool
   of the functions that can't be linked statically.  This could hardly
   be made completely transparent, though.
 
-* Godmar Back writes:
-  libltdl uses such stdio functions as fopen, fgets, feof, fclose, and others.
-  These functions are not async-signal-safe. While this does not make
-  libltdl unusable, it restricts its usefulness and puts an
-  unnecessary burden on the user.
-
-  As a remedy, I'd recommend to replace those functions with functions
-  that POSIX says are async-signal-safe, such as open, read, close.
-  This will require you to handle interrupted system calls and implement
-  fgets, but the former isn't hard and there's plenty of implementations
-  out from which you can steal the latter.
-
-  I believe relying on async-signal-safe functions to the greatest extent
-  possible would greatly improve libltdl's ability to be embedded in and
-  used by other systems.
-
 2.6. win32 support
 ------------------