Re: Question: LispWorks IDE with different CL engine?
"Marco Antoniotti (as marco dot antoniotti at unimib dot it)" <[email protected]>
| Newsgroups | gmane.lisp.lispworks.general |
|---|---|
| Message-ID | <CAG0Nw2mQ3Jj0GwDEJU-E2kcFUXsTWdUUHsaw1aDUYDu9CWHq8w@mail.gmail.com> |
Hi My suggestion is what others have made. Get it to run on LW and then pass it in SBCL trying to satisfy its often annoying notes and warnings. That's the way I work, and it has served me well. Portability is another issue. MA On Tue, Feb 3, 2026 at 10:07 AM Uģis Lācis (as ugis dot lacis at equa dot se) <[email protected]> wrote: > Hi Tim (and everyone who chimed in the discussion), > > > > Thanks for all the responses, interesting read. What I am doing, really, > is working in an old closed-source LISP code-base, which we are trying to > port from ACL 3.0.2 to modern LISP. Our aim is actually to be portable, > i.e., we hope to be able to use both LispWorks and SBCL (and potentially > some other LISP) for running our code. > > > > We have bought LispWorks primarily for the same reason as Paul mentioned, > ease of use and convenient debugging. This part I have found much harder to > use in SBCL (I have tried both SLIME and VSCode + Alive extension). What I > have determined is that SLIME is much more capable than VSCode (at least in > terms of inspecting CLOS structures), however, tricky to keep as everyday > tool (I guess EMACS buffers is the culprit ... I just have not had time or > managed to churn through the workflows there to come up with my own and fix > a cheat sheet ...). And due to this, my progress with SBCL is lagging > behind that of LispWorks. Sadly, as code base is quite large, we do not > have the option to (re)write it in LispWorks and run in SBCL; the fact is – > the current state does run worse in SBCL compared to LispWorks. > > > > So this is basically what I want to do – have as good debugging in SBCL as > I have in LispWorks. > > > > Regarding basic REPL, tracing, rudimentary breakpoints and annoying > stepping ... That works out of the box in VSCode + Alive, nothing needs > implementation there. > > > > Best, > Ugis > > > > *From:* Tim Bradshaw <[email protected]> > *Sent:* Monday, 2 February 2026 19:48 > *To:* Yuri Davidovsky <[email protected]> > *Cc:* Uģis Lācis <[email protected]>; [email protected] > *Subject:* Re: Question: LispWorks IDE with different CL engine? > > > > The question is not whether you can persuade the LW IDE to talk to SBCL > but what use is that, and is is worth the candle? > > > > If you're using the LW IDE you have a high-quality, deeply integrated CL *right > there*, in the same Lisp image as the IDE. That gives you most of the > things people liked about LispMs: the LW IDE is, by margin, the closest > thing to using a LispM I know of (it's not very like a LispM in interface > but the all-in-one-image thing is a big deal). Getting an implementation > that is sitting at the end of a bit of string to be anything like that nice > is going to be ... well, good luck with it > > > > I think we need to know what OP wants to achieve. > -- Marco Antoniotti, Professor, Director tel. +39 - 02 64 48 79 01 DISCo, University of Milan-Bicocca U14 2043 http://dcb.disco.unimib.it Viale Sarca 336 I-20126 Milan (MI) ITALY REGAINS: https://regains.disco.unimib.it/