Re: symbol conflicts

>>>>> "rif" == rif  <[email protected]> writes:

    rif> I can compile OK, but I (use :matlisp) encounters the problem that
    rif> there is already a symbol "real" in the common-lisp-user package.  I
    rif> can unintern it manually, but I don't know whether this is safe (I'm
    rif> not sure how to figure out what it does, it seems to be the name of a
    rif> class, rather than a function).  What's the right approach?

I thought I had fixed this so that the matlisp REAL symbol didn't
collide with the COMMON-LISP symbol.  Perhaps this is messed up?

The obvious work-around is not to do (use :matlisp), and do your work
in the matlisp package.


    rif> Also, for anyone using cllib (which I'd think could be many people),
    rif> there's also conflicts with "norm" and "dot".

I think that's what packages are for.  If you're going to do (use
:matlisp) and (use :cllib), you'll get this problem.  You have to
decide which NORM and DOT functions you really want by importing (or
shadow-importing) from the desired package.

Ray