From f5e9ed1ea965827f29fe0fa77a32e09737e51b45 Mon Sep 17 00:00:00 2001 From: Rusty Russell Date: Mon, 18 Jun 2012 22:30:27 +0930 Subject: ntdb: remove ntdb_error() It was a hack to make compatibility easier. Since we're not doing that, it can go away: all callers must use the return value now. Signed-off-by: Rusty Russell --- lib/ntdb/doc/TDB_porting.txt | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) (limited to 'lib/ntdb/doc') diff --git a/lib/ntdb/doc/TDB_porting.txt b/lib/ntdb/doc/TDB_porting.txt index 8df137416d..34e536ffcb 100644 --- a/lib/ntdb/doc/TDB_porting.txt +++ b/lib/ntdb/doc/TDB_porting.txt @@ -9,8 +9,7 @@ Interface differences between TDB and NTDB. - ntdb functions return NTDB_SUCCESS (ie 0) on success, and a negative error on failure, whereas tdb functions returned 0 on success, and -1 on failure. tdb then used tdb_error() to determine the error; - this is also supported in ntdb to ease backwards compatibility, - though the other form is preferred. + this API is nasty if we ever want to support threads, so is not supported. - ntdb's ntdb_fetch() returns an error, tdb's returned the data directly (or tdb_null, and you were supposed to check tdb_error() to find out why). -- cgit