[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CLOS bug? (Re: Plans for clisp, and pcl vs clisp clos)

To: clisp-list <clisp-list@ma2s2.mathematik.uni-karlsruhe.de>
Subject: Re: CLOS bug? (Re: Plans for clisp, and pcl vs clisp clos)
From: haible@ilog.ilog.fr (Bruno Haible)
Date: Tue, 25 Jul 95 14:13:55 +0200
In-reply-to: <9507251020.AA17773@candy.jsk.t.u-tokyo.ac.jp>
References: <9507251020.AA17773@candy.jsk.t.u-tokyo.ac.jp>

> 	c. It doesn't allow to redefine the generic function which has
> 	   different parameters from the original.

In clisp, you can redefine a generic function with different parameters
if you first FMAKUNBOUND it. Maybe clisp should be changed to do this
(by default) and emit a warning, instead of signalling an error.


Bruno Haible                        email: <haible@ilog.fr>
Software Engineer                   phone: +33-1-49083585

References:
- Re: CLOS bug? (Re: Plans for clisp, and pcl vs clisp clos)
  - From: tom@jsk.t.u-tokyo.ac.jp (Tomohiro Shibata)

Prev by Date: Re: CLOS bug? (Re: Plans for clisp, and pcl vs clisp clos)
Next by Date: not a release
Previous by thread: Re: CLOS bug? (Re: Plans for clisp, and pcl vs clisp clos)
Next by thread: problem with load
Index(es):
- Date
- Thread