From 1f5844000e11a4efda65c34fcd9af4e5f152b537 Mon Sep 17 00:00:00 2001 From: Han-Wen Nienhuys Date: Thu, 21 Aug 2008 23:16:20 -0300 Subject: Style nitpicks: space before () in function call. --- libguile/gc-malloc.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'libguile/gc-malloc.c') diff --git a/libguile/gc-malloc.c b/libguile/gc-malloc.c index 4e06f2f69..2f6ea21d8 100644 --- a/libguile/gc-malloc.c +++ b/libguile/gc-malloc.c @@ -119,7 +119,7 @@ scm_realloc (void *mem, size_t size) We don't want these sweep statistics to influence results for cell GC, so we don't collect statistics. - realloc() failed, so we're really desparate to free memory. Run a + realloc () failed, so we're really desparate to free memory. Run a full sweep. */ scm_i_sweep_all_segments ("realloc", NULL); @@ -314,7 +314,7 @@ scm_gc_malloc (size_t size, const char *what) again in scm_gc_register_collectable_memory. We don't really want the second GC since it will not find new garbage. - Note: this is a theoretical peeve. In reality, malloc() never + Note: this is a theoretical peeve. In reality, malloc () never returns NULL. Usually, memory is overcommitted, and when you try to write it the program is killed with signal 11. --hwn */ @@ -342,10 +342,10 @@ scm_gc_realloc (void *mem, size_t old_size, size_t new_size, const char *what) /* - scm_realloc() may invalidate the block pointed to by WHERE, eg. by + scm_realloc () may invalidate the block pointed to by WHERE, eg. by unmapping it from memory or altering the contents. Since - increase_mtrigger() might trigger a GC that would scan - MEM, it is crucial that this call precedes realloc(). + increase_mtrigger () might trigger a GC that would scan + MEM, it is crucial that this call precedes realloc (). */ decrease_mtrigger (old_size, what); -- cgit v1.2.3