[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
FYI: drop ltdl TODO item (no stdio)
From: |
Ralf Wildenhues |
Subject: |
FYI: drop ltdl TODO item (no stdio) |
Date: |
Thu, 7 Oct 2004 07:58:27 +0200 |
User-agent: |
Mutt/1.4.1i |
Applied to HEAD.
2004-10-07 Ralf Wildenhues <address@hidden>
* TODO: Remove item: no need for a libltdl without stdio.
Index: TODO
===================================================================
RCS file: /cvsroot/libtool/libtool/TODO,v
retrieving revision 1.54
retrieving revision 1.55
diff -u -r1.54 -r1.55
--- TODO 30 Sep 2004 20:53:17 -0000 1.54
+++ TODO 7 Oct 2004 05:53:44 -0000 1.55
@@ -137,22 +137,6 @@
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
------------------
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- FYI: drop ltdl TODO item (no stdio),
Ralf Wildenhues <=