diff options
| author | m8pple <dt10@imperial.ac.uk> | 2014-10-21 10:03:21 +0100 |
|---|---|---|
| committer | m8pple <dt10@imperial.ac.uk> | 2014-10-21 10:03:21 +0100 |
| commit | c13c865f5cc6902e6624d63ac89cc5d37b817d7b (patch) | |
| tree | 1452589dafba6d479ff47f1a849dc98ff3805201 | |
| parent | 5cff35f7d43cd2a610a4fa4d287bb73e21264747 (diff) | |
| download | MipsCPU-c13c865f5cc6902e6624d63ac89cc5d37b817d7b.tar.gz MipsCPU-c13c865f5cc6902e6624d63ac89cc5d37b817d7b.zip | |
Fixed #6 : ambiguity in mips_mem_free spec
| -rw-r--r-- | include/mips_mem.h | 2 |
1 files changed, 1 insertions, 1 deletions
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: |