From: Christophe R. <cs...@ca...> - 2014-07-20 12:23:59
|
Hi all, Could we please freeze development in favour of identifying and tracking down any regressions, for a release of sbcl-1.2.2 near the end of next week? As ever, reports of testing on applications and libraries, whether failures or successes, are most welcome. Best, Christophe |
From: Douglas K. <do...@go...> - 2014-07-21 13:09:33
|
I accidentally broke hash cache profiling in change 21d82cd3. Nobody should notice this unless they build from source and set the enabling switch to T: (eval-when (:compile-toplevel :load-toplevel :execute) (defvar *profile-hash-cache* nil)) Still, there's no reason to release known bad code... Fix it now, or later? |
From: Christophe R. <cs...@ca...> - 2014-07-21 13:28:16
|
Douglas Katzman <do...@go...> writes: > Still, there's no reason to release known bad code... Fix it now, or > later? I'd say now, please. Best, Christophe |
From: Zach B. <xa...@xa...> - 2014-07-22 16:17:44
|
Christophe Rhodes <cs...@ca...> writes: > Hi all, > > Could we please freeze development in favour of identifying and tracking > down any regressions, for a release of sbcl-1.2.2 near the end of next > week? As ever, reports of testing on applications and libraries, > whether failures or successes, are most welcome. I just tried building the Quicklisp world with 1.2.1.71-bc18b32, and there are a number of (related?) failures: - nuclblog: http://report.quicklisp.org/nuclblog/2014-07-22/failtail.txt - multiple-value-variants: http://report.quicklisp.org/multiple-value-variants/2014-07-22/failtail.txt - lol-re: http://report.quicklisp.org/lol-re/2014-07-22/failtail.txt - let-over-lambda: http://report.quicklisp.org/let-over-lambda/2014-07-22/failtail.txt - esrap-liquid: http://report.quicklisp.org/esrap-liquid/2014-07-22/failtail.txt - cl-larval: http://report.quicklisp.org/cl-larval/2014-07-22/failtail.txt - cl-secure-read: http://report.quicklisp.org/cl-secure-read/2014-07-22/failtail.txt - cl-read-macro-tokens: http://report.quicklisp.org/cl-read-macro-tokens/2014-07-22/failtail.txt - cl-yaclyaml: http://report.quicklisp.org/cl-yaclyaml/2014-07-22/failtail.txt I haven't done any analysis or bug reporting on these failures. Zach |
From: Douglas K. <do...@go...> - 2014-07-22 16:52:47
|
Most of those failures are from abuse of backquote in defmacro-enhance which is in turn used by other systems. If not due directly to defmacro-enhance, then due to similar ideas which are espoused by the author of (the text) let-over-lambda in which he seems to promote use of ideas that are easy to implement unportably but tricky to implement portably. defmacro-enhance lacks a self-test that exhibits the problem, which is why that system by itself seems to pass. The author of defmacro-enhance is aware of the issue. I never cc'd authors of the dependent systems, though I might do that if a fix is not forthcoming. I'll take a look at nuclblog as I don't recall that showing up on my watch list. |
From: Paul K. <pk...@gm...> - 2014-07-22 22:58:27
|
On Tue, Jul 22, 2014 at 12:52 PM, Douglas Katzman <do...@go...> wrote: > I'll take a look at nuclblog as I don't recall that showing up on my watch > list. nuclblog has been broken since May 2008 (https://github.com/andreas23/nuclblog/commit/ae3fca0f46f783fb1452d28b9b96d63c9911bfc1). It has `(... ,(cons blog '&key key-args) ...) instead of (I can only assume) `(... ,(list* blog '&key key-args) ...). Paul Khuong |
From: Cyrus H. <ch...@bo...> - 2014-07-23 11:45:02
|
Thanks Paul. Should be fixed now: https://github.com/slyrus/nuclblog Cyrus On Jul 23, 2014, at 12:58 AM, Paul Khuong <pk...@gm...> wrote: > On Tue, Jul 22, 2014 at 12:52 PM, Douglas Katzman <do...@go...> wrote: >> I'll take a look at nuclblog as I don't recall that showing up on my watch >> list. > > nuclblog has been broken since May 2008 > (https://github.com/andreas23/nuclblog/commit/ae3fca0f46f783fb1452d28b9b96d63c9911bfc1). > It has > > `(... ,(cons blog '&key key-args) ...) > > instead of (I can only assume) `(... ,(list* blog '&key key-args) ...). > > Paul Khuong > > ------------------------------------------------------------------------------ > Want fast and easy access to all the code in your enterprise? Index and > search up to 200,000 lines of code with a free copy of Black Duck > Code Sight - the same software that powers the world's largest code > search on Ohloh, the Black Duck Open Hub! Try it now. > http://p.sf.net/sfu/bds > _______________________________________________ > Sbcl-devel mailing list > Sbc...@li... > https://lists.sourceforge.net/lists/listinfo/sbcl-devel |
From: Douglas K. <do...@go...> - 2014-07-23 01:22:36
|
Thanks for finding these, Zach. multiple-value-variants is broken due to breakage in 'positional-lambda-2.0' which is apparently yet another system that defines a positional argument syntax. Not sure how I missed it, but yet again it's trying to grovel un-eval'd backquoted expressions. The common theme among the implementations of these constructions is that they're all naive in their code walking, and incidentally in their treatment of literal symbols that happen to coincide with the chosen syntax for positional args, which is irrelevant but interesting in that all such constructs were apparently designed using worse-is-better style. * (macroexpand-1 '(plambda `(funcall ,:1 ,:2))) => (LAMBDA () `(FUNCALL ,:|1| ,:|2|)) ; wrong Having looked at the source code for plambda, I'd probably rather just suggest that 'multiple-value-variants' not use the broken plambda. It's awfully obfuscated imho and I don't see any immediate fix. On Tue, Jul 22, 2014 at 12:10 PM, Zach Beane <xa...@xa...> wrote: > Christophe Rhodes <cs...@ca...> writes: > > > Hi all, > > > > Could we please freeze development in favour of identifying and tracking > > down any regressions, for a release of sbcl-1.2.2 near the end of next > > week? As ever, reports of testing on applications and libraries, > > whether failures or successes, are most welcome. > > I just tried building the Quicklisp world with 1.2.1.71-bc18b32, and > there are a number of (related?) failures: > > - nuclblog: http://report.quicklisp.org/nuclblog/2014-07-22/failtail.txt > > - multiple-value-variants: > http://report.quicklisp.org/multiple-value-variants/2014-07-22/failtail.txt > > - lol-re: http://report.quicklisp.org/lol-re/2014-07-22/failtail.txt > > - let-over-lambda: > http://report.quicklisp.org/let-over-lambda/2014-07-22/failtail.txt > > - esrap-liquid: > http://report.quicklisp.org/esrap-liquid/2014-07-22/failtail.txt > > - cl-larval: > http://report.quicklisp.org/cl-larval/2014-07-22/failtail.txt > > - cl-secure-read: > http://report.quicklisp.org/cl-secure-read/2014-07-22/failtail.txt > > - cl-read-macro-tokens: > http://report.quicklisp.org/cl-read-macro-tokens/2014-07-22/failtail.txt > > - cl-yaclyaml: > http://report.quicklisp.org/cl-yaclyaml/2014-07-22/failtail.txt > > I haven't done any analysis or bug reporting on these failures. > > Zach > > > ------------------------------------------------------------------------------ > Want fast and easy access to all the code in your enterprise? Index and > search up to 200,000 lines of code with a free copy of Black Duck > Code Sight - the same software that powers the world's largest code > search on Ohloh, the Black Duck Open Hub! Try it now. > http://p.sf.net/sfu/bds > _______________________________________________ > Sbcl-devel mailing list > Sbc...@li... > https://lists.sourceforge.net/lists/listinfo/sbcl-devel > |