I checked the base sources into SourceForge CVS and played with them
successfully, then went on to fixing bugs. I now have a version
0.6.7.2 on my machine at home, which was intended become a CVS
Alas, the relevant sourceforge machine, cvs.sbcl.sourceforge.net,
seems to be fried, refusing my connections or not responding at all.
sbcl.sourceforge.net refuses my connections too. Am I happy about
having committed the sources to a system which goes off line without
notice (and without any explanation I can find anywhere on the
SourceForge site)? Guess.
Version 0.6.7.2, languishing in my checked-out directory on my machine
at home, fixes the range-checking problems like (BUTLAST '(1 2 3) -1)
which were reported by Peter Van Eynde a while ago. There are also
some other minor changes, but I can't review my list of them because I
can't do 'cvs diff' now. (Does this help you guess?:-)
Hopefully this unscheduled and unexplained downtime is a not-to-be
repeated aberration, and after the scheduled downtime this weekend,
the sources can have a happy life at cvs.sbcl.sourceforge.net..
By the way, if anyone knows how to use pcl-cvs with ssh access to CVS
at SourceForge, please let me know. (cvs.sbcl.sourceforge.net doesn't
allow ordinary shell logins, so I can't set up my ~/.ssh/ directory,
so CVS needs a password every time it uses ssh, so pcl-cvs dies.)
William Harold Newman <william.newman@...>
PGP key fingerprint 85 CE 1C BA 79 8D 51 8C B9 25 FB EE E0 C3 E5 7C