suzanne.soy/racket
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request #36 from barak/master

Browse Source 
spelling
original commit: eb76dc73253e2fdb7ed1a411c301b6674a16c163
This commit is contained in:
R. Kent Dybvig 2016-05-04 20:17:16 -04:00
commit 245c1e460a
3 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
c/gcwrapper.c
View File

@ -130,7 +130,7 @@ void S_gc_init() {
S_G.countof_size[countof_guardian] = 0;
for (i = 0; i < countof_types; i += 1) {
if (Svector_ref(S_G.countof_names, i) == FIX(0)) {
fprintf(stderr, "unitialized countof_name at index %d\n", i);
fprintf(stderr, "uninitialized countof_name at index %d\n", i);
S_abnormal_exit();
}
}

2
c/scheme.c
View File

@ -620,7 +620,7 @@ static IBOOL find_boot(name, ext, errorp) const char *name, *ext; IBOOL errorp;
Sschemeheapdirs, Sdefaultheapdirs);
S_abnormal_exit();
} else {
if (verbose) fprintf(stderr, "no compatable %s%s found\n", name, ext);
if (verbose) fprintf(stderr, "no compatible %s%s found\n", name, ext);
return 0;
}
}

2
scheme.1.in
View File

@ -605,7 +605,7 @@ At optimize-levels 0, 1, and 2, code generated by the compiler is
At optimize-level 3, code generated by the compiler is \fIunsafe\fP,
i.e., may omit these checks.
Unsafe code is usually faster, but optimize-level 3 should be used only
for well-tested code since the absense of type and bounds checks may
for well-tested code since the absence of type and bounds checks may
result in invalid memory references, corruption of the Scheme heap (which
may cause seemingly unrelated problems later), system crashes, or other
undesirable behaviors.