Re: [asdf-devel] Make the CL syntax predictable

2014-03-15 Thread Attila Lendvai
> The clean thing to do would be to use named-readtables and/or > cl-syntax, and have each file evaluate (in-readtable :foo) or have a > perform :around method or around-compile hook that does it for you. [...] > Without ASDF, there's no way the libraries will be safe by default. well, there is,

Re: [asdf-devel] Make the CL syntax predictable

2014-03-15 Thread Faré
Dear Anton, can you do a cl-test-grid test with the code in the standard-syntax branch from git://common-lisp.net/projects/asdf/asdf.git (commit 2c1107) ? That branch has my "each system gets its own syntax" thing, based on a general-purpose "each system has a set of private variables" protocol.

Re: [asdf-devel] BUILD-OP

2014-03-15 Thread Faré
>>: Faré >: Robert > Well, but consider this hypothetical person who doesn't know what's > going to happen and who isn't familiar with ASDF already. > > S/he types (asdf:make "foo") and *either* gets foo loaded into his/her > lisp image or an executable file gets dropped onto his/her disk? > W

Re: [asdf-devel] Port of ASDF 3.1.0.94 to MKCL

2014-03-15 Thread Faré
On Sat, Mar 15, 2014 at 9:09 PM, Jean-Claude Beaudoin wrote: > > Here is, as previously mentioned, the git format-patch with the > modifications needed to port current ASDF head to MKCL 1.1.8 and later. This > has been tested on Linux Ubuntu 12.04 and MKCL 1.1.8 where it passes all 51 > tests of t

Re: [asdf-devel] Make the CL syntax predictable

2014-03-15 Thread Faré
On Sat, Mar 15, 2014 at 4:52 PM, Robert P. Goldman wrote: > Here is an example of a kind of system that will be broken by this > proposed change: > > * We have a distributed system that is lisp-based. > > * There is a small set of ASDF systems that constitutes the common base > of the modules of t

Re: [asdf-devel] BUILD-OP

2014-03-15 Thread Robert P. Goldman
Faré wrote: >> In that case, maybe instead of trying to take a real English word that >> > already has a meaning, we should take a short phrase that means exactly >> > what we will do: >> > >> > DO-DEFAULT-OPERATION-ON-SYSTEM >> > to be shortened to >> > DDO >> > >> > [I don't like DoS or DDoS for

Re: [asdf-devel] Make the CL syntax predictable

2014-03-15 Thread Robert P. Goldman
Here is an example of a kind of system that will be broken by this proposed change: * We have a distributed system that is lisp-based. * There is a small set of ASDF systems that constitutes the common base of the modules of this distributed system. * For each module, there is an ASDF system, wh

Re: [asdf-devel] Make the CL syntax predictable

2014-03-15 Thread Faré
On Sat, Mar 15, 2014 at 9:08 AM, Zach Beane wrote: > Faré writes: > >>> Should ASDF fail the libraries which modify global readtable - I doubt it's >>> ASDF role. >>> >> Yes it is, see my paper: >> http://fare.tunes.org/files/tmp/asdf/asdf3-2014.html#%28part._.Safety_before_.Ubiquity%29 > > So y

Re: [asdf-devel] Make the CL syntax predictable

2014-03-15 Thread Zach Beane
Faré writes: >> Should ASDF fail the libraries which modify global readtable - I doubt it's >> ASDF role. >> > Yes it is, see my paper: > http://fare.tunes.org/files/tmp/asdf/asdf3-2014.html#%28part._.Safety_before_.Ubiquity%29 So you want to make a change rapidly to suit the deadlines of a con