[Openmcl-devel] Docstring question
gb at clozure.com
Mon Sep 18 03:04:16 EDT 2006
It's probably some mixture of all of the above (er, below). MCL originally ran
on 1MB MacPlus machines, and eliminating doc strings from the memory image
(they were distributed in a separate file) was a simple way of trying to
keep the memory footprint small (if all doc strings added up to a few hundred
Kbytes, that would have had a very significant impact on things; getting
rid of them (moving them to a separate file) was low-hanging fruit.
OpenMCL started as an attempt to develop a lisp for embedded systems
(spacecraft, robots) and even though the constraints were a little
different that was still a memory-constrained environment, so some of
the things that MCL had done to keep the footprint small (like
neglecting to retain doc strings) were still useful.
It was only about a year ago that the bootstrapping processed started
preserving doc strings from the files in the level-0 directory, and
around that time that Bryan O'Connor tried to ensure that many CL
functions and variables and documented CCL package things had doc strings.
The original motivation for avoiding doc strings is, of course, long
On Sat, 16 Sep 2006, Phil wrote:
> Just curious, is there any reason (resource usage, preference,
> history, or other) for the minimal use of docstrings in the OpenMCL
> source code?
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
More information about the Openmcl-devel