CLISP Help Wanted

CLISP project founder Bruno Haible was one of the finalists for the 2002 Free Software Award! Note that it said:

"Bruno Haible (known for his work on GNU CLISP)" !

Now it is your chance to win the next Free Software Award!

The CLISP project is looking for excellent C and Lisp hackers who can enhance CLISP and add new features (see development sources).

The prizes for handling the issues listed below:

handle one issue and you get Mercurial write access;

handle two issues and you become an admin of the CLISP project;

handle three or more issues and you become the principal maintainer.

This reminds me of a joke: after the 1991 Russian coup attempt (whose failure lead to the final downfall of communism), the Communist Party was very unpopular and tried to increase the membership by asking the existing members to recruit new members, with the following incentives:

if you bring one new member, you don't have to pay membership dues

if you bring two new members, you may resign from the Party

if you bring three new members, you may resign and you will also receive a certificate that you have never been a member of the Party!

The CLISP tasks

Entry-level tasks

Add a magic module interfacing to libmagic. Add a uuid module for manipulation of UUIDs, interfacing to <uuid/uuid.h> on unix and to CoCreateGuid() on windows. Add a serial module to control serial devices using <termios.h> on unix and SetCommState() on windows.

Segmentation faults

Any hard crash (segmentation fault, bus error etc) is a bug in CLISP. See CLISP bug tracker.

Ongoing tasks

Searching for Common Lisp packages which do not run on CLISP and porting them to CLISP. Translate CLISP messages into new languages and update the existing translatons.

New features

Infrastructure

Use libtool to produce lisp.so ( lisp.dll on woe32) instead of lisp.run ( lisp.exe on woe32).

Use dlopen ( LoadLibrary on woe32) instead of exec ( CreateProcess on woe32) to start a linking set in clisp ( clisp.exe on woe32). This is related to embeddability.

Upgrade the Implementation notes DocBook infrastructure from v4 to v5.



See also