freenode/#lisp - IRC Chatlog
Search
23:39:11
White_Flame
even more literally: (defmacro defun-with-source (name params &body body) `(progn (register-source-code ',name ',params ',body) (defun ,name ,params ,@body)))
0:39:45
pjb
White_Flame: https://www.informatimago.com/develop/lisp/com/informatimago/small-cl-pgms/ibcl/index.html
0:55:44
White_Flame
I know there were some very simple Lisps for the C64; with that thing having much more ram it could have been more viable
1:08:28
v0|d
White_Flame: designing a board w/ more ram is painful w/o 4-6lyrs. Not sure they have the tech back in then.
1:17:42
White_Flame
I don't know the details of boad design that affects it, but I'll take your word there
1:20:07
v0|d
White_Flame: sry, I wasn't tryng to be right. Her eyou go https://www.youtube.com/watch?v=0YdLZAQSOa4
1:24:33
no-defun-allowed
just get this running in cc65 and you'll have half a lisp https://raw.githubusercontent.com/8l/openvmtil/master/lib/sl3.c
1:26:15
no-defun-allowed
i imagine you could pretend the c64 was a stack machine since there's few registers
1:28:36
White_Flame
I made my own 16-bit environment for the purpose: https://acheronvm.github.io/acheronvm/
6:36:02
asarch
One stupid question: Is SB-EXT:SAVE-LISP-AND-DIE the same with Smalltalk about the images?
6:37:04
beach
I don't know about Smalltalk images, but it saves the entire image into a "core" file that can then be used as an argument to start up SBCL later.
6:38:40
beach
People complain that it creates a big file, but that is a problem only if you are planning to create thousands of small applications, or if you have an embedded system with very little memory.
6:39:17
beach
Oh, and there is an option to create an executable file too, so no core file required in that case.
6:39:36
asarch
I studied the log from the other day (when I did a mess with packages) and I found what went wrong
6:39:40
zigpaw
they are close enough, there are some limitations you'll see more limiting in SBCL than in Squeak/Pharo, the "one active thread only" will prevent you from having gui app dumped to image, in smalltalk you get that taken care of itself.
6:40:46
asarch
Since I was desperate to make my example to work, I couldn't read that :clim cannot be used it directly
6:42:43
zigpaw
on the other hand, when learning sometimes it is good to do the not recommended, just to learn why it is so ;)
6:43:51
asarch
I found a working example at: /home/asarch/quicklisp/dists/quicklisp/software/mcclim-20180711-git/README.md
6:54:50
beach
But, in addition, it is recommended that you do not :USE packages other than a small number (I only ever :USE the COMMON-LISP package) that you trust not to change.
6:58:24
beach
Pretty much all I do from the REPL is to have ASDF compile a package, start an application, or run some tests.
6:58:31
zigpaw
when learning and writting throw-away code in repl, I think it is free-for-all if you know the rules/good-practices you are breaking ;-)
7:00:55
beach
And, yes, of course, you can't wait until you know all the rules before you start writing code.
7:08:29
aeth
I only :USE CL and my own libraries. If I broke something in the latter, I know it's my fault.
8:06:54
beach
So the Common Lisp HyperSpec explicitly allows for the implementation to define additional options for DEFGENERIC and DEFCLASS. I am wondering how existing implementations take advantage of this liberty and what additional options would benefit SICL.