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