Sophie

Sophie

distrib > Mandriva > 2010.0 > i586 > media > contrib-release > by-pkgid > 723830890bac44da3d113209b14e090b > files > 239

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

<html lang="en">
<head>
<title>Creating new operations - 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="up" href="Operations.html#Operations" title="Operations">
<link rel="prev" href="Predefined-operations-of-asdf.html#Predefined-operations-of-asdf" title="Predefined operations of asdf">
<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="Creating-new-operations"></a>
<p>
Previous:&nbsp;<a rel="previous" accesskey="p" href="Predefined-operations-of-asdf.html#Predefined-operations-of-asdf">Predefined operations of asdf</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="Operations.html#Operations">Operations</a>
<hr>
</div>

<!-- node-name,  next,  previous,  up -->
<h4 class="subsection">3.1.2 Creating new operations</h4>

<p>asdf was designed to be extensible in an object-oriented fashion.  To
teach asdf new tricks, a programmer can implement the behaviour he
wants by creating a subclass of <code>operation</code>.

   <p>asdf's pre-defined operations are in no way &ldquo;privileged&rdquo;, but it is
requested that developers never use the <code>asdf</code> package for
operations they develop themselves.  The rationale for this rule is
that we don't want to establish a &ldquo;global asdf operation name
registry&rdquo;, but also want to avoid name clashes.

   <p>An operation must provide methods for the following generic functions
when invoked with an object of type <code>source-file</code>:  <em>FIXME describe
this better</em>

     <ul>
<li><code>output-files</code>
<li><code>perform</code>
The <code>perform</code> method must call <code>output-files</code> to find out
where to put its files, because the user is allowed to override
<li><code>output-files</code> for local policy <code>explain</code>
<li><code>operation-done-p</code>, if you don't like the default one

   </ul>

   </body></html>