Re: Strange eval-after-load

[John Paul Wallington]

Alan Mackenzie <address@hidden> writes:

>     ;; Make edebug understand the macros.
>     (eval-after-load "edebug"
>       '(progn
>            (def-edebug-spec cc-eval-when-compile t)
>            (def-edebug-spec c-point t)
>            (def-edebug-spec c-set-region-active t)
>          ....
>          ))

How about getting rid of the (eval-after-load "edebug" '(progn ... ))
form and instead replacing the `def-edebug-spec' calls with (put
'mumble 'edebug-form-spec 'spec) at toplevel ?  Or alternatively
having those `def-edebug-spec' calls appear at toplevel where they
would be expanded to `put' calls when compiled provided that
`def-edebug-spec' is defined (untested) ?