freenode/lisp - IRC Chatlog
Search
7:25:18
jiny
thanks pjb . I installed gnu clisp . it seems to work fine. but clisp on wsl crashes when I run it. and I use low version of windows10 home edition. so I cant install new wsl2 version on my computer.
7:26:13
pjb
jiny: since sbcl already solved the problem, you might be able to provide a working patch easily enough.
7:28:22
red-dot
good luck with sbcl on Windows... perhaps WSL will work. For normal Windows, this just isn't a platform they care about.
7:28:48
red-dot
Say, does anyone know how to contact the gitlab.common-lisp.net folks? They sign up system is a bit broken
7:29:00
pjb
jiny: the thing is that sbcl understood the problem and corrected it for sbcl. So reading this patch you will be able to understand it, and to build a patch for any implementation, including clisp.
10:57:26
DrDuck
I saw Alan Kay alluring to some stuff Mccarthy wrote 50 years ago and essentually said it makes Mondads look like a cludge and waste of time
10:58:31
DrDuck
In his 'Situations, Actions, and Causal Laws' part of his 'Programs With Common Sense' paper
11:00:21
DrDuck
so i really have half a understanding of all of this. what did alan kay mean by that statement?
11:18:27
pjb
So monads are just a bad and awkward implementation of objects in purely functional programming languages.
11:22:47
White_Flame
monads don't really implement objects, in the I/O mutation hiding sense. They externalize them from the language
11:24:12
White_Flame
it merely is an interface to something external, where the interface itself is immutable
11:25:26
White_Flame
and of course, that was the main thrust of why monads were added to haskell, and then their other uses were promoted as well
11:29:27
DrDuck
so is there anything in common lisp that's as expressive/powerful as haskell typeclasses?
11:30:47
LdBeth
Typeclass is no more than a sophisticated ad hoc overloading => make ad hoc polymorphism less ad hoc
12:03:32
no-defun-allowed
but in any case, you could have a (not CL obviously) evaluator that treated numbers as non-self-evaluating, and then the type of the value of 123 is not necessasrily a number
12:12:00
pjb
LdBeth: not necessarily: (let* ((*read-base* 3.) (*print-base* *read-base*)) (prin1-to-string (read-from-string "123"))) #| --> "123" |#
14:54:28
Xach
beach: might the eclector errors here be caused by recent updates to eclector? http://report.quicklisp.org/2019-08-22/failure-report/sel.html#software-evolution-library_run-dump-store
15:24:42
scymtym
Xach: yes, eclector now exports READ{,-PRESERVING-WHITESPACE,-FROM-STRING} from its packages
15:30:01
scymtym
Xach: great. maybe recommend that they don't :USE eclector packages to avoid this kind of thing in the future