September 2009 - cltl3-devel@lists.common-lisp.net

[cltl3-devel] Fwd: RFC: CLtL3 Charter
by Gustavo 02 Sep '09

02 Sep '09

2009/9/1 <drew.crampsie(a)gmail.com> > > I'd personally much prefer a 'lispy' (read : verbose and understandable) > implementation of regexps then the one from perl, and still wouldn't want it > included as part of CLtL3.. > cl-ppcre allow the use of sexps as regexps. I think that they are "verbose" and "understandable".

1 0

[cltl3-devel] RFC: CLtL3 Charter
by Drew Crampsie 01 Sep '09

01 Sep '09

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 - 1) 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. 2) 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. 3) 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. 4) 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 5) 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.

3 2

[cltl3-devel] Fwd: RFC: CLtL3 Charter
by Gustavo 01 Sep '09

01 Sep '09

Sorry, drewc, the e-mail should have gone to the list, not only you. Hello, I also like to keep things simple. Here are a few suggestions, though. In paragraph 4, you didn't mention "sockets" explicitly in the list. I don't know if that is intended to be included in "Networking", because Unix sockets are local to the computer. A few more topics that could be discussed: (j) Interface to Environments, which is needed in a macro walker (e.g. cl-walker <http://common-lisp.net/project/cl-walker/> accesses lexical environments using implementation specific functions). (k)Custom Hash Functions and Hashtable Test (SBCL's extensions<http://www.sbcl.org/manual/Hash-Table-Extensions.html#Hash-Table-Extensions> ). (l) Weak Pointers, Weak Hashtables and Garbage Collector (like in trivial-garbage <http://www.cliki.net/trivial-garbage>). And, by the way, "omission" have only one "m". Cheers, Gustavo. 2009/8/31 Drew Crampsie <drewc(a)tech.coop> 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 - > > 1) 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. > > 2) 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. > > 3) 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. > > 4) 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 > > 5) 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(a)common-lisp.net > http://common-lisp.net/cgi-bin/mailman/listinfo/cltl3-devel >

1 0