diff options
author | Juanma Barranquero <lekktu@gmail.com> | 2011-11-15 01:54:19 +0100 |
---|---|---|
committer | Juanma Barranquero <lekktu@gmail.com> | 2011-11-15 01:54:19 +0100 |
commit | 0d26e0b62b7d01e3cb6eb57943269b8f25e53cd6 (patch) | |
tree | 784b0f664bd50cf4bc244141190d8b9c92973835 /src/ralloc.c | |
parent | 947cd66b9611a5c4c4eb60238022e72fe51e2e46 (diff) | |
download | emacs-0d26e0b62b7d01e3cb6eb57943269b8f25e53cd6.tar.gz |
Fix typos.
Diffstat (limited to 'src/ralloc.c')
-rw-r--r-- | src/ralloc.c | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/src/ralloc.c b/src/ralloc.c index 50d322523c1..62189ad8fc7 100644 --- a/src/ralloc.c +++ b/src/ralloc.c @@ -219,13 +219,13 @@ find_heap (POINTER address) If enough space is not presently available in our reserve, this means getting more page-aligned space from the system. If the returned space is not contiguous to the last heap, allocate a new heap, and append it + to the heap list. - obtain does not try to keep track of whether space is in use - or not in use. It just returns the address of SIZE bytes that - fall within a single heap. If you call obtain twice in a row - with the same arguments, you typically get the same value. - to the heap list. It's the caller's responsibility to keep - track of what space is in use. + obtain does not try to keep track of whether space is in use or not + in use. It just returns the address of SIZE bytes that fall within a + single heap. If you call obtain twice in a row with the same arguments, + you typically get the same value. It's the caller's responsibility to + keep track of what space is in use. Return the address of the space if all went well, or zero if we couldn't allocate the memory. */ @@ -389,7 +389,7 @@ find_bloc (POINTER *ptr) while (p != NIL_BLOC) { /* Consistency check. Don't return inconsistent blocs. - Don't abort here, as callers might be expecting this, but + Don't abort here, as callers might be expecting this, but callers that always expect a bloc to be returned should abort if one isn't to avoid a memory corruption bug that is difficult to track down. */ @@ -1180,7 +1180,7 @@ r_alloc_reset_variable (POINTER *old, POINTER *new) /* Find the bloc that corresponds to the data pointed to by pointer. find_bloc cannot be used, as it has internal consistency checks - which fail when the variable needs reseting. */ + which fail when the variable needs resetting. */ while (bloc != NIL_BLOC) { if (bloc->data == *new) |