Sophie: sbcl-1.0.31-1mdv2010.0 i586

sbcl-1.0.31-1mdv2010.0.i586.rpm

<html lang="en">
<head>
<title>TODO list - asdf Manual</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="asdf Manual">
<meta name="generator" content="makeinfo 4.13">
<link title="Top" rel="start" href="index.html#Top">
<link rel="prev" href="Getting-the-latest-version.html#Getting-the-latest-version" title="Getting the latest version">
<link rel="next" href="missing-bits-in-implementation.html#missing-bits-in-implementation" title="missing bits in implementation">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
This manual describes asdf, a system definition facility for Common
Lisp programs and libraries.

asdf Copyright (C) 2001-2004 Daniel Barlow and contributors

This manual Copyright (C) 2001-2004 Daniel Barlow and
contributors

Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and associated documentation files (the
``Software''), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:

The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED ``AS IS'', WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.-->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
  pre.display { font-family:inherit }
  pre.format  { font-family:inherit }
  pre.smalldisplay { font-family:inherit; font-size:smaller }
  pre.smallformat  { font-family:inherit; font-size:smaller }
  pre.smallexample { font-size:smaller }
  pre.smalllisp    { font-size:smaller }
  span.sc    { font-variant:small-caps }
  span.roman { font-family:serif; font-weight:normal; } 
  span.sansserif { font-family:sans-serif; font-weight:normal; } 
--></style>
</head>
<body>
<div class="node">
<a name="TODO-list"></a>
<p>
Next:&nbsp;<a rel="next" accesskey="n" href="missing-bits-in-implementation.html#missing-bits-in-implementation">missing bits in implementation</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="Getting-the-latest-version.html#Getting-the-latest-version">Getting the latest version</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="index.html#Top">Top</a>
<hr>
</div>

<!-- node-name,  next,  previous,  up -->
<h2 class="chapter">7 TODO list</h2>

<p>* Outstanding spec questions, things to add

   <p>** packaging systems

   <p>*** manual page component?

   <p>** style guide for .asd files

   <p>You should either use keywords or be careful with the package that you
evaluate defsystem forms in.  Otherwise (defsystem partition ...) 
being read in the cl-user package will intern a cl-user:partition
symbol, which will then collide with the partition:partition symbol.

   <p>Actually there's a hairier packages problem to think about too. 
in-order-to is not a keyword: if you read defsystem forms in a package
that doesn't use ASDF, odd things might happen

   <p>** extending defsystem with new options

   <p>You might not want to write a whole parser, but just to add options to
the existing syntax.  Reinstate parse-option or something akin

   <p>** document all the error classes

   <p>** what to do with compile-file failure

   <p>Should check the primary return value from compile-file and see if
that gets us any closer to a sensible error handling strategy

   <p>** foreign files

   <p>lift unix-dso stuff from db-sockets

   <p>** Diagnostics

   <p>A &ldquo;dry run&rdquo; of an operation can be made with the following form:

<pre class="lisp">     (traverse (make-instance '&lt;operation-name&gt;)
               (find-system &lt;system-name&gt;)
               'explain)
</pre>
   <p>This uses unexported symbols.  What would be a nice interface for this
functionality?

   </body></html>