RE: Question: LispWorks IDE with different CL engine?

Cool. Ok, thanks for suggestions, guys.

I am fully aware of that what I am doing is rather far from optimal and I would like to resolve all warnings etc. I actually started with that approach, but it rather soon became overwhelming, pace was extremely slow, etc ... That is why we decided to focus on critical errors (not sure if right term, but those that stops compiler from loading/compiling) and postpone actual debugging to run-time ... Especially because that is really convenient with LispWorks.

But at this stage, it could be good to revisit this and have another go. Code coverage I guess I could also try and see where I get.

Thanks again for the time you put in the discussion!
/Ugis

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of joswig (as joswig at lisp dot de)
Sent: Tuesday, 3 February 2026 12:59
To: [email protected]
Subject: Re: Question: LispWorks IDE with different CL engine?



> Am 03.02.2026 um 12:06 schrieb Tim Bradshaw (as tfb at cley dot com) <[email protected]>:
> 
> Ignoring compiler warnings is a huge mistake in my opinion.  You need to make them go away, both because every warning is the compiler telling you 'I think this is a bug' and you shouldn't ignore bugs, and because anything that compiles with a vast spew of noise means you never see the noise that matters: it's the 'all the warning lights have come on on the control panel and I have no idea what is happening now' while all the coolant pours out of the reactor problem.
> 
> 

One of the nice features of LispWorks is the Compilation Conditions tool in the IDE.
This helps to work on the compiler warnings and errors.





_______________________________________________
Lisp Hug - the mailing list for LispWorks users [email protected] http://www.lispworks.com/support/lisp-hug.html

_______________________________________________
Lisp Hug - the mailing list for LispWorks users
[email protected]
http://www.lispworks.com/support/lisp-hug.html