meval should not have to be protected unless it is called
from a program like pdisrep, which uses the 'raw' genvars,
and in which it again calls ratdisrep.
Any call to meval from pdisrep would be, in my view,
a mistake waiting to happen.
The gensym program that tacks x onto a number instead
of calling them all g0123, g0124, .... looks cute but
seems to be bad idea if the SAME print name is used for
different symbols. The way maxima seems to be set up, you
have confusing printouts, and unnecessarily so. In theory
one could have all gensyms with the same print name, in some
bizarre attempt to save memory perhaps. This seems dumb.
Shouldn't the counter be incremented so that
#:|x21773| can only occur once? Is this a bug in GCL?
Does this problem occur in all Lisps?
RJF