I pushed your changes and fixed the character encoding problem for CLisp (by changing #\Form to (code-char 12)).<br><br>There are, however, still many tests that fail.  The bulk of these failures are because of semantically meaningless differences in parenscript-compiled javascript and the expected javascript.  for example:
<br><br>Failure Details:                                                                                                                                                                           <br> --------------------------------                                                                                                                                                           
<br> METHOD-CALL-LAMBDA-CALL []: (NORMALIZE-JS-CODE JS-CODE) evaluated to "(function (x) {return x;                                                                                                                    <br>
})(10).toString()", which is not STRING= to "(function (x) {                                                                                                                                <br>return x;                                                                                                                                                                                   
<br>})                                                                                                                                                                                          <br>(10).toString()"..   
<br><br>It is worth considering using a Javascript parser compare expected vs. compiled Javascript instead of using the slight hack in the current testing code.<br><br>Anyhow, now that 5am is compiling we might want to get tests working again.
<br><br>Thanks,<br>Red<br><br><div><span class="gmail_quote">On 7/1/07, <b class="gmail_sendername">Luca Capello</b> <<a href="mailto:luca@pca.it">luca@pca.it</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello!<br><br>On Fri, 22 Jun 2007 20:33:15 +0200, Vladimir Sedach wrote:<br>> Ok, then I'll just wait for your fix.<br><br>The FiveAM problem was fixed with the latest patches, but now there's<br>a new problem with 
parenscript.test, in part similar to [1]:<br><br>--8<---------------cut here---------------start------------->8---<br>; /var/cache/common-lisp-controller/1000/sbcl/local/home/luca/Hacking/debdarcs/parenscript-upstream/t/test-
package.fasl written<br>; compilation finished in 0:00:00<br>; compiling file "/home/luca/Hacking/debdarcs/parenscript-upstream/t/test.lisp" (written 17 JUN 2007 09:22:25 PM):<br>; compiling (IN-PACKAGE :JS-TEST)
<br>; compiling (DEFUN TRIM-WHITESPACE ...)<br>; compiling (DEFUN SAME-SPACE-BETWEEN-STATEMENTS ...)<br>; compiling (DEFUN NO-INDENTATION ...)<br>; compiling (DEFUN NO-TRAILING-SPACES ...)<br>; compiling (DEFUN NORMALIZE-JS-CODE ...)
<br>; compiling (DEFMACRO TEST-PS-JS ...)<br>; compiling (DEFUN RUN-TESTS ...)<br>; compiling (DEF-SUITE PS-TESTS)<br>; compiling (IN-SUITE PS-TESTS)<br>debugger invoked on a SIMPLE-ERROR in thread #<THREAD "initial thread" {10025DEB61}>:
<br>  Unkown suite PS-TESTS.<br><br>Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.<br><br>restarts (invokable by number or by possibly-abbreviated name):<br>  0: [CONTINUE] Create a new suite named PS-TESTS.
<br>  1: [RETRY   ] Retry performing #<ASDF:COMPILE-OP NIL {10044E5901}> on<br>                #<ASDF:CL-SOURCE-FILE "test" {1003214501}>.<br>  2: [ACCEPT  ] Continue, treating #<ASDF:COMPILE-OP NIL {10044E5901}> on
<br>                #<ASDF:CL-SOURCE-FILE "test" {1003214501}> as having been<br>                successful.<br>  3: [ABORT   ] Exit debugger, returning to top level.<br><br>(NIL)<br>0]<br>--8<---------------cut here---------------end--------------->8---
<br><br>This can be solved with the same patch as at [1] (darcs patch<br>attached), but then the compilation stops again:<br><br>--8<---------------cut here---------------start------------->8---<br>; compiling (TEST-PS-JS DOT-NOTATION-BUG ...)
<br>; compiling (TEST-PS-JS METHOD-CALL-OP-FORM ...)<br>; compiling (TEST-PS-JS METHOD-CALL-NUMBER ...)<br>; compiling (TEST-PS-JS METHOD-CALL-STRING ...); compilation aborted because of fatal error:<br>;   READ failure in COMPILE-FILE:
<br>;     READER-ERROR at 2528 (line 82, column 44) on #<SB-SYS:FD-STREAM for "file /home/luca/Hacking/debdarcs/parenscript-upstream/t/test.lisp" {10032C80C1}>:<br><br><br>; /var/cache/common-lisp-controller/1000/sbcl/local/home/luca/Hacking/debdarcs/parenscript-upstream/t/test.fasl written
<br>; compilation finished in 0:00:01<br>; illegal terminating character after a colon: #\<br>WARNING:<br>   COMPILE-FILE warned while performing #<COMPILE-OP NIL {1003A661E1}> on<br>   #<CL-SOURCE-FILE "test" {10039BFF91}>.
<br><br>debugger invoked on a ASDF:COMPILE-FAILED in thread #<THREAD "initial thread" {10025DEB61}>:<br>  erred while invoking #<COMPILE-OP NIL {1003A661E1}> on<br>  #<CL-SOURCE-FILE "test" {10039BFF91}>
<br><br>Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.<br><br>restarts (invokable by number or by possibly-abbreviated name):<br>  0: [RETRY ] Retry performing #<ASDF:COMPILE-OP NIL {1003A661E1}> on
<br>              #<ASDF:CL-SOURCE-FILE "test" {10039BFF91}>.<br>  1: [ACCEPT] Continue, treating #<ASDF:COMPILE-OP NIL {1003A661E1}> on<br>              #<ASDF:CL-SOURCE-FILE "test" {10039BFF91}> as having been
<br>              successful.<br>  2: [ABORT ] Exit debugger, returning to top level.<br><br>((SB-PCL::FAST-METHOD ASDF:PERFORM (ASDF:COMPILE-OP ASDF:CL-SOURCE-FILE))<br> #<unavailable argument><br> #<unavailable argument>
<br> #<ASDF:COMPILE-OP NIL {1003A661E1}><br> #<ASDF:CL-SOURCE-FILE "test" {10039BFF91}>)<br>0]<br>--8<---------------cut here---------------end--------------->8---<br><br>This one is probably a typo, in fact removing the colon solves it
<br>(darcs patch attached).<br><br>However, the compilation is successful only on SBCL-1.0.6.0, because<br>on CLisp-2.41 (both on a Debian sid) I get:<br><br>--8<---------------cut here---------------start------------->8---
<br>;; Compiling file /home/luca/var/lib/debdarcs/parenscript-upstream/t/test-package.lisp ...<br>;; Wrote file /var/cache/common-lisp-controller/1000/clisp/local/home/luca/var/lib/debdarcs/parenscript-upstream/t/test-package.fas
<br>;; Loading file /var/cache/common-lisp-controller/1000/clisp/local/home/luca/var/lib/debdarcs/parenscript-upstream/t/test-package.fas ...<br>;; Loaded file /var/cache/common-lisp-controller/1000/clisp/local/home/luca/var/lib/debdarcs/parenscript-upstream/t/test-
package.fas<br>;; Compiling file /home/luca/var/lib/debdarcs/parenscript-upstream/t/test.lisp ...<br>*** - READ from #<INPUT BUFFERED FILE-STREAM CHARACTER #P"/home/luca/var/lib/debdarcs/parenscript-upstream/t/test.lisp" @212>: there is no character with name "FORM"
<br>The following restarts are available:<br>RETRY          :R1      Retry performing #<ASDF:COMPILE-OP NIL #x000333D42988> on #<ASDF:CL-SOURCE-FILE "test" #x000333CFAC80>.<br>ACCEPT         :R2      Continue, treating #<ASDF:COMPILE-OP NIL #x000333D42988> on #<ASDF:CL-SOURCE-FILE "test" #x000333CFAC80> as having been successful.
<br>ABORT          :R3      ABORT<br>Break 1 JS-TEST[3]><br>--8<---------------cut here---------------end--------------->8---<br><br>Commenting out line 212 in test.lisp solves the problem.  Is my CLisp<br>too old or is something other?
<br><br>Thx, bye,<br>Gismo / Luca<br><br>Footnotes:<br>[1] <a href="http://common-lisp.net/pipermail/bese-devel/2007-July/003044.html">http://common-lisp.net/pipermail/bese-devel/2007-July/003044.html</a><br><br><br>_______________________________________________
<br>parenscript-devel mailing list<br><a href="mailto:parenscript-devel@common-lisp.net">parenscript-devel@common-lisp.net</a><br><a href="http://common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel">http://common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel
</a><br><br><br></blockquote></div><br>