Context Navigation

Things To Do

Here are some big and small things that would be good to do. If you would be interested in funding any of these,
please send mail to business@…. If you would be interested in volunteering to
work on any of these, that would be welcome, too. Please send mail to openmcl-devel@…
to discuss any of them.

Microsoft Windows

The 32-bit Windows lisp doesn't currently run on 64-bit Windows. This
is because 64-bit Windows doesn't let us set up an x86 LDT so that we
can use a segment register to point to thread-local data. A possible
solution to this is to pare down the size of the TCR so that we can fit
as many slots as possible into the Windows TLS vector.

Documentation

We could really use better documentation tools. We had a long thread on
openmcl-devel about it, but there seems to be no magic way to make editing
Docbook content easier.

Release Tools

Building binaries for releases is currently a tedious manual process.
There are currently 14 sets of binaries to build. Automating this would be a real
time-saver.

A buildbot that builds and tests ccl regularly. In addition to ccl's own test suite,
it would be desirable to run and test other major software. For instance,
Maxima has a substantial test suite.

IDE stuff

Unbundle the Cocoa-based IDE from the ccl distribution and make it
available separately.

Add and document a reasonble way to create NSStrings/CFStrings from
lisp strings. There's unexported stuff like %make-nsstring and
ccl::with-autoreleased-nsstrings, but there needs to be something
official.

Design and implement some sort of windowing library for MS Windows
that doesn't rely on Cocotron. Maybe something for X11, too. (Note
that ccl doesn't have any idea how to call C++, so it's best to pick
a library with a C interface.)

Ports to More Systems

At some point, the Darwin/PPC is going to die (not least because we'll run
out of working hardware). The PPC Linux port will likely live on, but we'll
probably need to acquire some newer hardware one of these days.