headers
Erik Huelsmann | 18 Aug 2012 16:29
Picon
Gravatar

SLIME && ABCL autoloaders

Hi Mark,


While working on the autoloaders, I found a very interesting thing: SLIME doesn't know about ABCL's autoloaders.

To maximize the benefit of SLIME for ABCL (yea, I even started using it to debug ABCL itself, after you pointed out to me that these tools generally help productivity), I think it would be beneficial to teach it about autoloaders.

The case I'm talking about is this: When using M-. SLIME looks up the source code location for the source associated with the symbol. However, when you do that to a symbol which hasn't been autoloaded yet, that source code location information isn't available. SLIME could easily resolve that by evaluating the form (SYS::RESOLVE <symbol>) and look for the info after that.

SLIME could do the same when looking up function lambda list information to present in the minibuffer for auto-completion.

How about that?

Bye,

Erik.
_______________________________________________
armedbear-devel mailing list
armedbear-devel@...
http://lists.common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel
Permalink | Reply |
headers
Stas Boukarev | 18 Aug 2012 18:38
Picon

Re: SLIME && ABCL autoloaders

Erik Huelsmann <ehuels@...> writes:

> Hi Mark,
>
> While working on the autoloaders, I found a very interesting thing: SLIME
> doesn't know about ABCL's autoloaders.
>
> To maximize the benefit of SLIME for ABCL (yea, I even started using it to
> debug ABCL itself, after you pointed out to me that these tools generally
> help productivity), I think it would be beneficial to teach it about
> autoloaders.
>
> The case I'm talking about is this: When using M-. SLIME looks up the
> source code location for the source associated with the symbol. However,
> when you do that to a symbol which hasn't been autoloaded yet, that source
> code location information isn't available. SLIME could easily resolve that
> by evaluating the form (SYS::RESOLVE <symbol>) and look for the info after
> that.
Sounds good, done in CVS.

> SLIME could do the same when looking up function lambda list information to
> present in the minibuffer for auto-completion.
Looks like it already does this.

--

-- 
With best regards, Stas.
Permalink | Reply |
headers
Stas Boukarev | 18 Aug 2012 18:38
Picon

Re: [armedbear-devel] SLIME && ABCL autoloaders

Erik Huelsmann <ehuels <at> gmail.com> writes:

> Hi Mark,
>
> While working on the autoloaders, I found a very interesting thing: SLIME
> doesn't know about ABCL's autoloaders.
>
> To maximize the benefit of SLIME for ABCL (yea, I even started using it to
> debug ABCL itself, after you pointed out to me that these tools generally
> help productivity), I think it would be beneficial to teach it about
> autoloaders.
>
> The case I'm talking about is this: When using M-. SLIME looks up the
> source code location for the source associated with the symbol. However,
> when you do that to a symbol which hasn't been autoloaded yet, that source
> code location information isn't available. SLIME could easily resolve that
> by evaluating the form (SYS::RESOLVE <symbol>) and look for the info after
> that.
Sounds good, done in CVS.

> SLIME could do the same when looking up function lambda list information to
> present in the minibuffer for auto-completion.
Looks like it already does this.

--

-- 
With best regards, Stas.
Permalink | Reply |

Gmane