Re: :around methods on LOAD-OP and COMPILE-OP

> "Attila Lendvai" <[email protected]> writes:
>
>>> I also think that the try-recompiling restart for compile-op is
>>> useless, because asdf already sets up a retry restart
...
>
>> does the original retry restart always recompile? i think sometimes  
>> it
>> happens that the file actually compiles but with some warning
...
>
> The annoying case is when compile-op succeeds (no compilation errors
> or full warnings) but the subsequent load-op signals an error (say
> because some class is not yet defined).  At that point, the retry
> restart will attempt to reload the fasl -- not completely useless, but
> needing a little bit more manual intervention.  It is for removing
> that manual intervention that the try-recompiling restart is most
> useful, I think; simply edit the source file and select that restart.
> But for compile-op failures, I think the TRY-RECOMPILING and RETRY
> restarts have equivalent behaviour.
>

Yes.

I use "try recompiling" a fair amount when in exactly this situation  
(the compile went fine; the load failed). It seems that it should be  
possible to know whether we're loading or compiling and not include  
the restart in the latter case. That would be a good thing, yes?

--
Gary Warren King, metabang.com
Cell: (413) 559 8738
Fax: (206) 338-4052
gwkkwg on Skype * garethsan on AIM





-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/