On Tue, Feb 26, 2013 at 2:18 AM, Attila Lendvai
attila.lend...@gmail.com wrote:
Or I could rely on SBCL being used a whole lot and indeed having
immutable such default syntax tables with understandable messages
to blame whoever tries to mutate those tables without rebinding them
this approach
Or I could rely on SBCL being used a whole lot and indeed having
immutable such default syntax tables with understandable messages
to blame whoever tries to mutate those tables without rebinding them
this approach seems to be the most straightforward to me.
especially since we have that great
On Thu, Feb 21, 2013 at 4:46 PM, Juan Jose Garcia-Ripoll
juanjose.garciarip...@gmail.com wrote:
On Wed, Feb 20, 2013 at 11:18 PM, Faré fah...@gmail.com wrote:
Implementations that make the standard readtable read-only:
allegro sbcl
Implementations that don't:
abcl ccl clisp cmucl ecl
Fare == Far Far writes:
Fare For the record, checking on my machine today:
Fare Implementations that make the standard readtable read-only:
Fare allegro sbcl
Fare Implementations that don't:
Fare abcl ccl clisp cmucl ecl lispworks scl
FWIW, on cmucl, *readtable* is a copy
Fare == Far Far writes:
Fare On Thu, Feb 21, 2013 at 2:08 PM, Raymond Toy toy.raym...@gmail.com
wrote:
Fare == Far Far writes:
Fare For the record, checking on my machine today:
Fare Implementations that make the standard readtable read-only:
Fare allegro sbcl
On Wed, Feb 20, 2013 at 11:18 PM, Faré fah...@gmail.com wrote:
Implementations that make the standard readtable read-only:
allegro sbcl
Implementations that don't:
abcl ccl clisp cmucl ecl lispworks scl
This is not true
(with-standard-io-syntax
(set-dispatch-macro-character #\! #\Y
Dear Common Lisp hackers,
Inspecting with Anton Vodonosov the latest batch of cl-test-grid issues
when running with asdf 2.29.x, we found an interesting case
that mirrors the previous failure of iolib 0.7.3 with 2.29.
In the hope of making the semantics of asd files more deterministic,
with an
21.02.2013, 00:45, Faré fah...@gmail.com:
Or I could remove the with-standard-io-syntax altogether, and say
yes, if you're doing any global modification, you suck and you're
going to break something for someone, but that's none of my business.
Anton leans for the latter.
I meant not that
