SBCL Internals : TODO

SBCL Internals
The pages on this CLiki-driven site can be edited by anybody at any time. No warranty of any kind can therefore be made; any implied warranties of merchantability or fitness for a particular purpose are expressly disclaimed

[ Home ]

[ Recent Changes ]

[ About CLiki ]

[ Text Formatting ]

Interested in hacking on SBCL? Here are some places to look for features we (primarily the developers, who will tend to edit this page if anything truly ridiculous is added) would like but haven't yet had time/motivation to do

In the source tree, see the TODO and BUGS files, and grep the tree for FIXMEs. On this CLiki see also Wishlist.

On this CLiki, the following pages are in the TODO topic:

Block compilation - Block compilation
Callbacks - Almost there
Function Name Validation - Redundant code-paths: could use a cleanup, but non-critical
Fwrapper - Nikodemus thinks having an exported interface would be good
One Point Zero - Some people think SBCL is useful already
serve-event - Documentation is missing
STEP - Numerous shortcomings remain as, but as of 0
The Manual - The current SBCL manual is missing bits ("entire key chapters") in places, and the order it tackles subjects is based mostly on CMUCL rather than anything that makes sense
THREADING - SBCL has alpha-quality support for multiple threads, currently only on x86 and x86-64 Linux
TRACE - Several outstanding issues

Pages in this topic: Block compilation Callbacks Function Name Validation Fwrapper One Point Zero serve-event STEP The Manual THREADING TRACE

Also linked from: index stack allocation

CLiki pages can be edited by anyone at any time. Imagine a fearsomely comprehensive disclaimer of liability. Now fear, comprehensively