2009-06-18 Marcus Brinkmann <[email protected]>

	* gpgme.h.in (GPGME_CONF_PATHNAME): Remove obsolete macro.

	* w32-io.c (_gpgme_io_pipe): Allocate reader/writer thread right
	away.
	(_gpgme_io_read, _gpgme_io_write, _gpgme_io_select)
	(_gpgme_io_dup): Never allocate threads here.
	(find_writer, find_reader): Check return value of thread creation
	function.

1 files changed, 5 insertions, 9 deletions

diff --git a/TODO b/TODO
index d84b2956..adbfb936 100644
--- a/TODO
+++ b/TODO
@@ -8,24 +8,20 @@ Hey Emacs, this is -*- org -*- mode!
    we block reading the next line with assuan.
 
 * Before release:
-** Figure out if _gpgme_io_pipe should pre-create reader/writer and if we
-   then can use !start_it in most invocations.  Note that gpgme_io_dup
-   probably should always use !start_it, because currently it will
-   always create reader/writer if they don't exist(!?).
 ** Some gpg tests fail with gpg 1.3.4-cvs (gpg/t-keylist-sig)
    The test is currently disabled there and in gpg/t-import.
 ** When gpg supports it, write binary subpackets directly,
    and parse SUBPACKET status lines.
-** A few months after 1.1.7:
-   Remove GPGME_CONF_PATHNAME macro.
 
 * ABI's to break:
+** Implementation: Remove support for old style error codes in
+   conversion.c::_gpgme_map_gnupg_error.
 ** gpgme_edit_cb_t: Add "processed" return argument
    (see edit.c::command_handler).
 ** I/O and User Data could be made extensible.  But this can be done
    without breaking the ABI hopefully.
-** All enums that should be enums need to have a maximum value to ensure
-   a certain minimum width for extensibility.
+** All enums should be replaced by ints and simple macros for
+   maximum compatibility.
 ** Compatibility interfaces that can be removed in future versions:
 *** gpgme_data_new_from_filepart
 *** gpgme_data_new_from_file
@@ -109,7 +105,7 @@ Hey Emacs, this is -*- org -*- mode!
    the fds unregistered immediately - i think so?)
    Note that we need support in gpgsm to set include-certs to default
    as RESET does not reset it.
-** Optimize the case where a data object has 0an underlying fd we can pass
+** Optimize the case where a data object has an underlying fd we can pass
    directly to the engine.  This will be automatic with socket I/O and
    descriptor passing.
 ** Move code common to all engines up from gpg to engine.