18 May 2004 19:26
matlisp "pollutes" the common-lisp-user package
rif <rif <at> MIT.EDU>
2004-05-18 17:26:13 GMT
2004-05-18 17:26:13 GMT
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 ------------------------------------------------------- This SF.Net email is sponsored by: SourceForge.net Broadband Sign-up now for SourceForge Broadband and get the fastest 6.0/768 connection for only $19.95/mo for the first 3 months! http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
I'll see what I can do about it.
Ray
-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
RSS Feed