How to use Common Lisp kind of like a smalltalk image

purpose

I would like my general Lisp environment (SBCL + GNU Emacs + Slime) to look like a Smalltalk image in which I want to have a big ball of dirt in all my code organized in packages, and preferably projects, In other words, I messed up a bit with save-lisp-and-dieand installed Lisp in Emacs to open the saved image. Where I got lost is the right way to get him to work with Swank.

Problem

I believe that before you save-lisp-and-dieneed to put swank hooks inside my Lisp image. But that seems a little fragile, because when either my SBCL version or Slime version changes, it seems to throw a version mismatch.

Question

Am I missing something? Do people work this way or tend to be a more separate project as a downloadable set of packages under ASDF?

I really miss the Smalltalk method and feel that every ASDF project is a bit clunkier and more embedded in the file system. In comparison, this reminds me of too much of any other language and their orientation to the application / project. OTOH seems a little more stable, and re-versions are package dependent. Well, the whole hellish hellish language in different languages ​​is another matter.

Any tips on how to do what I want, or why this is not such a good idea, would be greatly appreciated.

+4
source share
1 answer

Images

Lisp , SBCL. Lisp 60- .

Smalltalk Lisp. Smalltalk (OS, runtime,...) - . SBCL OTOH .

Smalltalk . Smalltalk . Lisp, - , Xerox Interlisp - .

Lisp /IDE - Xerox Interlisp - AFAIK.

DEFSYSTEM

Common Lisp defsystem, ASDF IDE, GNU Emacs + SLIME, . , .

, Lisp, , . , .

Lisp

Lisp SBCL

  • FASL

/ . , .

, / .

SBCL , . : LispWorks. LispWorks , .

SLIME

, SLIME (SLIME, Lisp), . , SLIME.

+4

Source: https://habr.com/ru/post/1694674/


All Articles