Re: LISP Package

[shebs%utah-orion@utah-cs.arpa (Stanley Shebs)]

In PCLS we've been very careful to export only standard things from LISP,
and use SYSTEM for anything that is PCLS dependent.  The theory is that
it only takes one unqualified PCLS-specific symbol to ruin a programmer's
whole day - porting is hard enough when the necessary changes are obvious!
Even assuming something that every implementation "should have" (like
MULTIPLE-VALUE-SETF) is questionable.

I like Scott's suggestion of another package that exports exactly those
symbols defined in the standard.  Existing user programs needn't change,
and if a user wanted to test for portability, s/he could tweak the list
of default use packages from (LISP ...) to (STANDARD), and see what
happens to the program...

							stan