From: <Bil...@pe...> - 2004-10-29 00:12:12
|
Apparently this is correct behaviour - please ignore earlier email I sent with Helmut's patch. - Bill ----- Forwarded by Bill Clementson/PeopleSoft on 10/28/2004 06:10 PM ----- "Christophe Rhodes" <cs...@ca...> To: sli...@co... Sent by: cc: (bcc: Bill Clementson/PeopleSoft) slime-devel-bounces@comm Subject: [slime-devel] Re: CLISP support broken in CVS on-lisp.net 10/28/2004 03:53 PM Helmut Eller <e96...@st...> writes: > Bil...@pe... writes: > >> FYI - CLISP 2.33 support seems to be broken in CVS. Here's the contents of >> the *inferior-lisp* buffer when I attempt to load CLISP: > [snip] >> Current point in control string: >> Value: ~D = #x~X = #o~O = #b~:,,' ,8B = ~E >> | >> Break 1 SWANK[2]> > > I think this control string is legal and CLISP is broken. It's not, and clisp is quite right, though its error message is somewhat poor. In SBCL: * (format nil "~:,,' ,8B" 1) debugger invoked on a SB-FORMAT:FORMAT-ERROR in thread 3429: error in FORMAT: parameters found after #\: or #\@ modifier ~:,,' ,8B ^ See also: The ANSI Standard, Section 22.3 Cheers, Christophe _______________________________________________ slime-devel site list sli...@co... http://common-lisp.net/mailman/listinfo/slime-devel |