freenode/#sicl - IRC Chatlog
Search
5:11:13
beach
Some of the functionality that I am currently using full function calls for, like ENCLOSE, and now CATCH and UNWIND, could be at fixed locations in the executable. They are independent of the particular environment, so they don't have to be tied to any particular global environment. And they probably don't have to be full Common Lisp function calls, so they could use a simpler (and therefore cheaper) call protocol.
5:12:02
beach
But most importantly, they don't have to become part of every static environment. And so they don't have to be processed by closure conversion.
6:26:36
beach
This time it was Emacs suddenly taking nearly 100% of the CPU and none of my Emacs windows were refreshed. It went on for several minutes, and I finally decided to restart.
6:27:24
beach
Other times it has been Xorg basically grinding my computer to a halt. I am guessing because it is leaking memory.
6:28:03
no-defun-allowed
I've had weird race (possibly) conditions running some code in the REPL and M-dotting some other function while I wait, which end up in Emacs halting.
6:28:09
beach
And Firefox that does an automatic update, but does not preserve (it can't) the workspace of each window, so when it comes back, the windows are all in one workspace.
6:30:04
no-defun-allowed
Yeah, Firefox also weirds out sometimes, but it's usually it crashing for no reason and the "Please restart Firefox now that you updated it" messages.
6:34:21
no-defun-allowed
Do you remember what the first free Common Lisp implementation was, and when it was released?
6:35:55
beach
So there must have been a time when there were several partial implementations, and of CLtL1 at the time.
6:35:56
jackdaniel
(I remember when I was making the CL implementation graph, I've memorized some of such information)
6:36:50
no-defun-allowed
Firefox was released in 2002, Mozilla 1998, Netscape 1994. My guess is someone didn't want to rewrite all that browser stuff in a higher language at some point (or to update the browser for new standards).
6:38:08
beach
Well, they are programming C++ which changes all the time. They could have used Franz Lisp and then followed evolution to CLtL1 and then CLtL2.