I'll second (or third?) the appreciation of the simplicity.
Two questions though:
1. What exactly does "Editing" in (i) imply? I could guess (esp. with it being lumped with "Introspection"), but I'll hold off on assuming things...
2. While the "OS and Filesystem access" point is one I'm especially keen on, I'd like to hear what anyone's opinion would be on CLTL3 standardized regex functionality. Mr. Weitz's cl-ppcre seems to be fairly widely used & may be the *de-facto* standard, but why not take it one step further?
Just food for thought.
:ian
On Mon, Aug 31, 2009 at 2:57 PM, Drew Crampsie drewc@tech.coop wrote:
Hello all,
Below is a draft of the charter for the CLtL3 project. Please comment as you see fit.
Cheers,
drewc
Purposes of the CLtL3 effort. SECOND DRAFT - 2009-08-31 -
- The CLtL3 group wishes to create an updated description of Common
Lisp. It should codify existing practice and provide additional features to facilitate portability of code among diverse implementations.
- The group intends the description to be a base for a larger "standard
library" of code. The focus of the effort will be to provide library authors with a stable and portable lisp on which to build an evolving distribution that meets the ever changing needs of modern developers.
- The group will begin with ANSI Common Lisp as described in the
_Common Lisp Hyperspec_. All possible effort will be made to ensure source compatibility. The group does not intend to remove any functionality from the language, and will only deprecate features that are superseded by those in CLtL3.
- The group will address the following topics in the course of
producing the description. Preference will be given to topics that cannot be implemented portably and have multiple existing implementations.
(a) Repairing mistakes, ambiguities, and minor ommissions in ANSI Common Lisp (b) Extensions outlined in the CDR (including the MOP) (c) Multiprocessing and Concurrency (d) Foreign Function Interfaces (e) Extensible Streams (f) Extensible Sequences (g) Networking (h) OS and Filesystem access (i) Editing and Introspection
- The CLtL3 effort will be a community effort.Discussion will take
place on public forums. Any source code or documents produced will be placed under a permissive open source license that also allows commercial use and redistribution.
cltl3-devel mailing list cltl3-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/cltl3-devel