From c13c865f5cc6902e6624d63ac89cc5d37b817d7b Mon Sep 17 00:00:00 2001 From: m8pple Date: Tue, 21 Oct 2014 10:03:21 +0100 Subject: Fixed #6 : ambiguity in mips_mem_free spec --- include/mips_mem.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/mips_mem.h b/include/mips_mem.h index 97724ff..9a62422 100644 --- a/include/mips_mem.h +++ b/include/mips_mem.h @@ -103,7 +103,7 @@ mips_error mips_mem_write( really know what is being released (it could be memory, it could be file handles), and shouldn't care. Calling mips_mem_free on an empty (zero) handle is legal. Calling mips_mem_free twice on the - same handle is illegal, and the resulting behaviour is undefined + same non-empty handle is illegal, and the resulting behaviour is undefined (most likely a crash). A pattern that can be useful is: -- cgit