Hi!
Thanks for the hint. I took a look at sources. Both solutions have
their advantages.
Slime-asdf works in any CL which supports SLIME. My solution works in
SBCL and Lispworks only but does not require SLIME.
Either variant can be prefferred in different situations.
What goes to name coersion,
On 7/10/15 Jul 10 -5:46 AM, 73budden . wrote:
> I see you mean situation where we have systems
>
> (defsystem "Bad2")
> (defsystem "bAd2")
> (defsystem :|baD2|)
>
> In this case we can navigate to :|baD2| by name :bad2, and unable to
> navigate to first two systems. Where should I err? According
I see you mean situation where we have systems
(defsystem "Bad2")
(defsystem "bAd2")
(defsystem :|baD2|)
In this case we can navigate to :|baD2| by name :bad2, and unable to
navigate to first two systems. Where should I err? According to
coerce-name rules, :|baD2|, :bad2 and "bad2" are identical
Hi!
>> I believe *current-component* is rather innocent
>NOT AT ALL.
Design choices is a great topic for holywar :) If variables are not
innocent for you, then you just not accept my patch. I'll continue to
use it for myself. Unfortunately, I have no time and desire to reshape
it, at least in the
On Thu, Jul 9, 2015 at 3:07 PM, 73budden . wrote:
>> Why would a file be loaded through the wrong system?
> Sorry, I have no time to dig into techical details of that kind.
>
Well, if we don't understand the error model, we can't devise a proper fix.
How is the solution I offer not satisfactory?
> Why would a file be loaded through the wrong system?
Sorry, I have no time to dig into techical details of that kind. I
believe *current-component* is rather innocent and sometimes useful,
but this is not so important. What I want, is that editing feature
would be available to all asdf users. How
> But what about "normal" operation? E.g. I use "of-system" to declare and
> assert
> that the file is loaded through a correct system. Only a special
> variable works there as there is no condition at all.
>
Why would a file be loaded through the wrong system? Is it something
likely to happen? Ho
Hi!
> You 'access' a debugger stack by using handler-bind and restart-case.
> Then the user uses the debugger that can use the annotations. This
> modular design is a great strength of CL.
Yes, I was wrong. It is easy to capture condition with handler-bind
and restart-case.
But what about "normal"
