Release Digest: GNU, March 21, 2004
Mar 22, 2004, 05:00 (0 Talkback[s])
Re-Imagining Linux Platforms to Meet the Needs of Cloud Service Providers
GNU CLISP 2.33
Common Lisp is a high-level, general-purpose programming
language. GNU CLISP is a Common Lisp implementation by Bruno Haible
of Karlsruhe University and Michael Stoll of Munich University,
both in Germany. It mostly supports the Lisp described in the ANSI
Common Lisp standard. It runs on microcomputers (Windows
NT/2000/XP, Windows 95/98/ME) as well as on Unix workstations
(Linux, SVR4, Sun4, DEC Alpha OSF, HP-UX, BeOS, NeXTstep, SGI, AIX
and others) and needs only 2 MB of RAM. It is Free Software and may
be distributed under the terms of GNU GPL, while it is possible to
distribute commercial applications compiled with GNU CLISP.
The user interface comes in German, English, French, Spanish, Dutch
GNU CLISP includes an interpreter, a compiler, a debugger, CLOS, a
foreign language interface, sockets, i18n, fast bignums and more.
An X11 interface is available through CLX, Garnet, CLUE/CLIO. GNU
CLISP runs Maxima, ACL2 and many other Common Lisp packages.
More information at
Sources and selected binaries are available by anonymous ftp
and its mirrors.
- Improved portability for nearly all platforms: Linux, MacOS X,
Solaris, Tru64, HP-UX, AIX, FreeBSD, NetBSD, OpenBSD, BeOS.
- Removed Acorn RISCOS support.
- Removed AmigaOS support.
- Removed support for MSDOS and OS/2, using EMX.
- Removed support for Borland C compiler on Win32.
- Added FFI support for x86_64 (AMD64) Linux and PowerPC MacOS
Sam Steingold (http://www.podval.org/~sds)
Programming is like sex: one mistake and you have to support it for
GNU Libidn 0.4.2 alpha
GNU Libidn is an implementation of the Stringprep, Punycode and
IDNA specifications defined by the IETF Internationalized Domain
Names (IDN) working group, used for internationalized domain names.
The library contains a generic Stringprep implementation that does
Unicode 3.2 NFKC normalization, mapping and prohibitation of
characters, and bidirectional character handling. Profiles for
Nameprep, iSCSI, SASL and XMPP are included. Punycode and ASCII
Compatible Encoding (ACE) via IDNA are supported. A mechanism to
define Top-Level Domain (TLD) specific validation tables, and to
compare strings against those tables, is included. Default tables
for some TLDs are also included.
Here are the compressed sources:
Here are GPG detached signatures:
Here are the build reports for various platforms:
Here are the MD5 and SHA1 signatures:
Noteworthy changes since version 0.4.0 (the last version
- Version 0.4.2 (released 2004-03-20)
- A Punycode implementation in Java was added, by Oliver Hitz.
Eventually hopefully a StringPrep, Nameprep and IDNA implementation
will be added as well. Currently you need to specify --enable-java
to enable the Java interface. The Java sources (below java/) are
compiled into byte-code (not native code) into a JAR library.
- More translations. Added Danish (by Morten Bo Johansen), French
(by Michel Robitaille), Polish (by Jakub Bogusz), and Serbian (by
- Norwegian TLD table added, by Thomas Jacob.
- API and ABI is backwards compatible with the previous
- Version 0.4.1 (released 2004-03-08)
- The user messages from the command line utility are now
translated. Currently English and Swedish is supported.
- Logic of stringprep_locale_charset modified. Future versions
will use, in order, $CHARSET iff defined, nl_langinfo (CODESET) iff
working, or fall back to returning "ASCII". Earlier it attempted to
guess the system locale, in contrast with the current application's
locale, via some setlocale save/set/reset magic. This change may
require you to invoke setlocale() in your application, which is
(should be) required for non-ASCII to work anyway. Based on
discussion with Ulrich Drepper.
- The command-line utility now invoke setlocale (LC_ALL, "") at
- Fixed SASLprep tables to prohibit non-ASCII space in output.
Non-ASCII space has always been mapped to ASCII space, so it is not
clear this really have any effect, but the specification require
- Building Libidn as part of GLIBC has been updated. Refer to
libc/README for more information. Incidentally, GLIBC in CVS now
include a copy of Libidn.
- API and ABI is backwards compatible with the previous version.
IDNA_DLOPEN_ERROR: ADD. Only used internally by Libidn in