From: Raymond T. <to...@rt...> - 2000-07-27 21:45:42
|
I'm trying to test f2cl with Clisp. Everything basically works, but I get the following problems. 1. Clisp complains about redefining the macro //. However, I can't find any such macro in Clisp. I see the special variable, but that's it. 2. Clisp complains about redefining the function REAL. However, I can't find any such function in Clisp. I see that it names a type and a class, but that's it. I could change f2cl to use something besides // and REAL, but I'd like to know if this is a problem with f2cl or Clisp. I don't have any such problems with CMUCL. Ray |
From: Bruno H. <ha...@il...> - 2000-07-27 21:54:23
|
Raymond Toy writes: > > I'm trying to test f2cl with Clisp. Everything basically works, but I > get the following problems. > > 1. Clisp complains about redefining the macro //. However, I can't > find any such macro in Clisp. I see the special variable, but > that's it. > > 2. Clisp complains about redefining the function REAL. However, I > can't find any such function in Clisp. I see that it names a type > and a class, but that's it. > > I could change f2cl to use something besides // and REAL, but I'd like > to know if this is a problem with f2cl or Clisp. It's a portability problem with your code. If you define a function or macro on a symbol that's not in a package of yours, it can collide if other people do the same thing. Bruno |
From: Raymond T. <to...@rt...> - 2000-07-27 22:07:57
|
>>>>> "Bruno" == Bruno Haible <ha...@il...> writes: Bruno> It's a portability problem with your code. If you define a Bruno> function or macro on a symbol that's not in a package of Bruno> yours, it can collide if other people do the same thing. Ok. I note that f2cl apparently used to be in its own package, but the original authors changed that so that it was in USER. I guess it should probably be changed back. Thanks, Ray |
From: Sam S. <sd...@gn...> - 2000-07-27 22:21:06
|
> * In message <4ne...@rt...> > * On the subject of "Clisp and REAL" > * Sent on 27 Jul 2000 17:45:40 -0400 > * Honorable Raymond Toy <to...@rt...> writes: > > 1. Clisp complains about redefining the macro //. > 2. Clisp complains about redefining the function REAL. These symbols, '//' and 'real', are exported from the package LISP. You should not change any slots of a symbol in a locked package. You will have the same problem with Allegro. You will be much better off if you do not redefine symbols that you do not own. -- Sam Steingold (http://www.podval.org/~sds) Micros**t is not the answer. Micros**t is a question, and the answer is Linux, (http://www.linux.org) the choice of the GNU (http://www.gnu.org) generation. I'd give my right arm to be ambidextrous. |