tdb2: rework some io.c functions to encode errors in their pointer returns.
This causes a subtle enhancement in tdb_direct(): it previously returned NULL on both "can't use direct access" or "some error occurred", as the caller always uses read/write functions as a fallback anyway. Now we distinguish the error case.
Showing
Please register or sign in to comment