restarts vs debugger command
fahree at gmail.com
Fri Jul 10 01:33:23 UTC 2015
On Thu, Jul 9, 2015 at 3:07 PM, 73budden . <budden73 at gmail.com> 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?
> I believe *current-component* is rather innocent
NOT AT ALL. Each and every new special variable is more state that may
cause interference or be victim of interference, has to be documented
or to cause maintainers to pray that no one will ever use, etc.
Peppering the code with gratuitous special variables is very bad
design and hell to test.
> and sometimes useful,
You didn't establish usefulness. Feel free to have your handlers use
special variables if you believe that help, but the core of ASDF will
try to not add more of them unless strictly necessary.
> but this is not so important. What I want, is that editing feature
> would be available to all asdf users. However, I'm not sure I'm ready
> to change something in my implementaion. Code I have just works in the
> way which satisfies me. I see you catched the idea, so now you can
> implement it yourself in a form which you think is better. In fact, it
> requres about a dozen lines of code only together with customizible
> editor hook.
Sorry, but it sounds like what you need is write a patch for your
debugger, not for asdf.
> What do you think about
> (keywordize (string-upcase (coerce-name name)))
Sounds good (at least assuming no one's using mlisp), but then issue
an error if it doesn't convert back to the same name when you
coerce-name it back.
These people are terrified that they will have to make a decision
about what to do and then do it."
"Don't tax me, don't tax thee, tax the fellow behind the tree."
— Senator Russell B. Long, chair of the Senate Finance Committee,
summarizing the principle of "tax reform" legislation.
More information about the asdf-devel