freenode/lisp - IRC Chatlog
Search
20:41:34
nicklaf
or, no, i was right the first time: "It's an eloquent testimony to the dangers of dynamic scope that even the very first example of higher-order Lisp functions was broken because of it. It may be that McCarthy was not fully aware of the implications of dynamic scope in 1960."
20:42:24
tfb
nicklaf: incidentally it looks like Standard Lisp (which is what I learnt, really) has just this weirdness: see http://user.ceng.metu.edu.tr/~ucoluk/research/lisp/generalinfo.html (the PDF report, p16)
20:45:51
tfb
I think it was also a lisp-1 (at least, something I used in that era was): lisp-1s with dynamic scope can be ... exciting, in bad ways
21:03:37
pfdietz
I have wondered if the scheme-ish approach of compiling with continuations would be useful for a CL compiler where one would want to be able to recompile functions even when they are on the current call stack (for example, if class definitions changed).
21:17:44
amerlyq
pfdietz: sounds like a good way to splash your brain matters over walls. Execute half of continuation, then recompile, and... continue from the middle of "somewhere"
23:30:20
Josh_2
Worked out how to do clicking with xlib thanks to this :) https://github.com/VitoVan/cl-dino/blob/master/cl-autogui.lisp
3:52:55
aeth
Josh_2: I got that, too, but on Gitlab. They all use the same Ruby package that has a really simple regex and for newlisp it's something like "define-" which is ridiculous because CL has define-condition and lots of custom macros
3:53:30
aeth
Josh_2: The workaround is to add a new .gitattributes file and have this be the one line: *.lisp linguist-language=Common Lisp
3:57:16
aeth
as far as I'm concerned, that's part of the mandatory CL git boilerplate now, along with e.g. a gitignore that ignores all of the FASLs