Re: [cclan-list] :around methods on LOAD-OP and COMPILE-OP

[Christophe R. <cs...@ca...>]

"Attila Lendvai" <att...@gm...> writes:

>> I also think that the try-recompiling restart for compile-op is
>> useless, because asdf already sets up a retry restart; I'd like to
>> delete it, but I have a sneaking suspicion that someone will complain
>> if I do.  If I don't hear confirmation about that, I'll delete it
>> anyway and suck up the consequences.
>
> does the original retry restart always recompile? i think sometimes it
> happens that the file actually compiles but with some warning and due
> to that asdf stops with an error. in such a situation the original
> retry restart will not try to recompile the file, only reload it.
> probably the same applies to load-time errors.
>
> i admit that i may be missing something, or maybe i was ignorant when
> dealing with asdf restarts, but i did use try-recompiling often
> recently.

I think you are missing something.

If the compile-op fails (i.e. if compile-file returns a true tertiary
value), the retry restart will retry the compile-op, so you can go and
edit the file and ask for a recompilation that way.

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.

Best,

Christophe