From ...
Path: archiver1.google.com!news2.google.com!news.maxwell.syr.edu!uio.no!nntp.uio.no!not-for-mail
From: Erik Naggum <erik@naggum.no>
Newsgroups: comp.lang.lisp
Subject: Re: Question about &rest, &key, and &allow-other-keys
Date: 19 Jan 2004 05:12:45 +0000
Organization: Naggum Software, Oslo, Norway
Lines: 16
Message-ID: <3283477965760092KL2065E@naggum.no>
References: <wj0oet13yth.fsf@five-percent-nation.mit.edu> <3283450606806605KL2065E@naggum.no> <wj0d69gy4ze.fsf@five-percent-nation.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: readme.uio.no 1074489165 28744 129.240.65.210 (19 Jan 2004 05:12:45 GMT)
X-Complaints-To: abuse@uio.no
NNTP-Posting-Date: Mon, 19 Jan 2004 05:12:45 +0000 (UTC)
Mail-Copies-To: never
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
Xref: archiver1.google.com comp.lang.lisp:10269

* rif <rif@mit.edu>
| So if I have scenarios A and B and C, I need different sets of
| defaults for each scenarios, with the additional ability to specify
| individual parameters manually.  For this reason, I don't think
| :CONSTRUCTOR can help me either, as I need several different sets of
| defaults.

  I suggested that you /investigate/ the :CONSTRUCTOR option to DEFSTRUCT
  for a reason.  Please take a better look at it and notice that it may
  be repeated.  This really is just what you need.

-- 
Erik Naggum | Oslo, Norway

Act from reason, and failure makes you rethink and study harder.
Act from faith, and failure makes you blame someone and push harder.