Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
johsteffens authored Jul 25, 2018
1 parent d165ef6 commit 31c3c1b
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -96,7 +96,7 @@ Concurrency is governed by a mutex. This means that memory management is not loc
### Mixing code using other memory managers
Tbman does not affect the behavior of other memory managers (such as `malloc`, `free`, `realloc`), so you can mix code using different management systems.
However, you can not manage the **same memeory instance** with a different manager. Meaning that you must use `tbman_free` or `tbman_realloc` on memory created with `tbman_malloc` or `tbman_realloc`. You can not use `free` or `realloc` on such an instance. The opposite applies too: You can not use `tbman_free` or `tbman_realloc` on memory created with `malloc`, `realloc`, `new` or any other non-tbman alloctor.
However, you can not manage the **same memory instance** with different managers. Meaning that you must use `tbman_free` or `tbman_realloc` on a memory instance allocated with `tbman_malloc` or `tbman_realloc`. You can not use `free` or `realloc` on such an instance. The opposite applies too: You can not use `tbman_free` or `tbman_realloc` on a memory instance allocated with `malloc`, `realloc`, `new` or any other non-tbman allocator.
<a name="anchor_motivation"></a>
## Motivation
Expand Down

0 comments on commit 31c3c1b

Please sign in to comment.