On Thu, Aug 28, 2008 at 5:06 PM, David Creelman
> I've got an app I'm writing that has something like (defconstant error
> "Error Message")
> The way I'm testing my code is to make a change to the code then load it
> again and see how it goes.
> Only problem is, when I redefine the constant I get an error that I'm forced
> to interact with (I'm getting pretty good at quickly hitting 0).
> Is there some way to prevent the defconstant errors?
See the Fine Manual:
If the constants are not really constants at them moment (you keep
changing them), then using a DEFPARAMETER is probably better. You can
always switch to DEFCONSTANT when things settle down.
> Is this a bad way to debug things?
Well, it depends. Often it may be preferable to simply C-c C-c the new
definitions in Slime -- but there are definitely cases where one wants
to reload everything.