Re: [E] new compiler error re: SET-DISPATCH-MACRO-CHARACTER

2017-10-12 Thread Faré
On Thu, Oct 12, 2017 at 6:53 PM, Stelian Ionescu wrote: > On Thu, 2017-10-12 at 13:03 -0500, Robert Goldman wrote: >> That may be, but it was unfair to get angry at the ASDF maintainers >> about this. This is just a pre-existing error that was *manifested* >> because of a

Re: [E] new compiler error re: SET-DISPATCH-MACRO-CHARACTER

2017-10-12 Thread Stelian Ionescu
On Thu, 2017-10-12 at 13:03 -0500, Robert Goldman wrote: > That may be, but it was unfair to get angry at the ASDF maintainers  > about this.  This is just a pre-existing error that was *manifested*  > because of a change in ASDF.  It's not our fault that this error  > appeared, it's not our fault

Re: [E] new compiler error re: SET-DISPATCH-MACRO-CHARACTER

2017-10-12 Thread Faré
On Thu, Oct 12, 2017 at 6:11 PM, Robert Goldman wrote: >> I will merge this into master, but do not have time to make a new release, >> or even test much this week or next. >> >> So this will simply remain in master for now. > > This patch is now available in ASDF 3.3.0.1 > I

Re: [E] new compiler error re: SET-DISPATCH-MACRO-CHARACTER

2017-10-12 Thread Robert Goldman
On 12 Oct 2017, at 13:08, Robert Goldman wrote: On 12 Oct 2017, at 13:04, Faré wrote: For those in a hurry for a fix, here is the merge request: https://gitlab.common-lisp.net/asdf/asdf/merge_requests/85 I will merge this into master, but do not have time to make a new release, or even

Re: [E] new compiler error re: SET-DISPATCH-MACRO-CHARACTER

2017-10-12 Thread 73budden .
Wow! Good news. 2017-10-12 21:08 GMT+03:00, Robert Goldman : > On 12 Oct 2017, at 13:04, Faré wrote: > >> For those in a hurry for a fix, here is the merge request: >> https://gitlab.common-lisp.net/asdf/asdf/merge_requests/85 > > I will merge this into master, but do not

Re: [E] new compiler error re: SET-DISPATCH-MACRO-CHARACTER

2017-10-12 Thread Robert Goldman
On 12 Oct 2017, at 13:04, Faré wrote: For those in a hurry for a fix, here is the merge request: https://gitlab.common-lisp.net/asdf/asdf/merge_requests/85 I will merge this into master, but do not have time to make a new release, or even test much this week or next. So this will simply

Re: [E] new compiler error re: SET-DISPATCH-MACRO-CHARACTER

2017-10-12 Thread Faré
On Thu, Oct 12, 2017 at 5:09 PM, 73budden . wrote: > Warning about modifying standard readtable is issued by SBCL (at least > in my SBCL 1.3.18), please grep for the message in SBCL sources, and > it seem to be introduced in 1.0.24. I took a look at puri's definition > (maybe

Re: [E] new compiler error re: SET-DISPATCH-MACRO-CHARACTER

2017-10-12 Thread Robert Goldman
On 12 Oct 2017, at 12:53, Konstanski, Carlos wrote: All signs point at puri being the culprit. I am absolutely not disagreeing with that. I provided the offending code in the bug report myself. The question is: what to do about it? The project is dead. The home page is gone. Here is what I

Re: [E] new compiler error re: SET-DISPATCH-MACRO-CHARACTER

2017-10-12 Thread 73budden .
Warning about modifying standard readtable is issued by SBCL (at least in my SBCL 1.3.18), please grep for the message in SBCL sources, and it seem to be introduced in 1.0.24. I took a look at puri's definition (maybe old, in my local copy of quicklisp) and it looks like it actually tries to

Re: [E] new compiler error re: SET-DISPATCH-MACRO-CHARACTER

2017-10-12 Thread 73budden .
Warning about modifying standard readtable is issued by SBCL (at least in my SBCL 1.3.18), please grep for the message in SBCL sources, and it seem to be introduced in 1.0.24. I took a look at puri's definition (maybe old, in my local copy of quicklisp) and it looks like it actually tries to

Re: [E] new compiler error re: SET-DISPATCH-MACRO-CHARACTER

2017-10-12 Thread Robert Goldman
I'm with Faré on this one. I don't see evidence that this change is because ASDF is doing something bad. I believe it's consistent with the hypothesis that there was some imperfectly-controlled aspect of building that is done differently now (e.g., files loaded in a different order where

Re: WARNING: System definition file ...

2017-10-12 Thread Faré
On Thu, Oct 12, 2017 at 7:17 AM, Stas Boukarev wrote: > Yes, SBCL has a deprecation process that goes through several stages which > span several years. QUIT signals a style-warning, not warning, and is > unlikely to ever signal a warning and will never go away. > .asd files

Re: WARNING: System definition file ...

2017-10-12 Thread Stas Boukarev
Yes, SBCL has a deprecation process that goes through several stages which span several years. QUIT signals a style-warning, not warning, and is unlikely to ever signal a warning and will never go away. If you're willing to fix all the affected systems just go through quicklisp, it'll have

Re: WARNING: System definition file ...

2017-10-12 Thread Faré
On Thu, Oct 12, 2017 at 6:00 AM, Stas Boukarev wrote: > I get 12 warnings with "System definition file contains definition for > system . Please only define and secondary systems with a name starting with > in that file." while loading a single project. > These are valid

Re: WARNING: System definition file ...

2017-10-12 Thread Stas Boukarev
I get 12 warnings with "System definition file contains definition for system . Please only define and secondary systems with a name starting with in that file." while loading a single project. How do I disable these warnings? If we are to update ASDF in SBCL I want to make the asdf.lisp version