[cltl3-devel] RFC: CLtL3 Charter

Stanislaw Halik sthalik at test123.ltd.pl
Mon Sep 14 17:52:14 UTC 2009


drew.crampsie at gmail.com writes:

> ANSI included FORMAT and LOOP, and similar arguments could have been
> (and were) made against them.

ANSI CL included lots of useless cruft because little children that
formed the commission threatened to pull out if crufts from their
implementation weren't supported. It wasn't enough for them if there was
a compatibility package (for instance „cl-maclisp”), they wanted to have
all that in the „cl” package.

I don't think there's much reason to standardize regexes, sockets and
the like. If something's implemented as a library, setting it in stone
with a specification actually makes matters worse. It only appeases
jerks blaming CL for „not having sockets” because there's no standard
library for IO. If CLtL3 implements sockets, they'll find a new thing to
blame CL for.

-- 
polscy Lispnicy, łączmy się -- #lisp-pl na freenode
Lisp stuff: <http://tehran.lain.pl>





More information about the Cltl3-devel mailing list