[Matlisp-devel] matlisp "pollutes" the common-lisp-user package

[rif <ri...@MI...>]

The matlisp "start.lisp" file operates in the package
common-lisp-user.  It defines a function setlogicalroot, which takes a
parameter r.  This definition causes the symbol r to be interned in
the common-lisp-user package.  Therefore, when I have another package
that exports a function named r, I get a conflict.  The workarounds
are simple (I already have another package that loads matlisp and
includes my utilities on top of matlisp, where I also unexport REAL,
so I just unintern R immediatly after loading matlisp, which will work
OK assuming I don't change the order in which I load matlisp and my
library) , but is it really good policy for a library to intern
symbols in cl-user?

rif