freenode/#lisp - IRC Chatlog
Search
5:07:06
pillton
(Sorry. I was thinking about our discussion.) I think the problem boils down to finding the right balance between normal order reduction and applicative order reduction.
5:10:57
pillton
I have for years been trying to decide whether I want to cross over the line and wade through compiler design and implementation.
5:20:42
beach
SICL is (in my opinion, of course) a unique opportunity to create a modern Common Lisp implementation from scratch, so if we have new ideas on how to make it fast while still keeping it highly maintainable, this is the time to do it. Just to give you more information to help you decide. :)
8:19:35
shrdlu68
This is pretty neat, has anyone had success running it? https://www.cliki.net/Epilog%20System%20and%20Episodic%20Logic
9:26:01
jackdaniel
pillton: since SICL uses full CL as its host language working on implementing it should be quite pleasent and not much different than working on other Common Lisp applications
12:45:02
jackdaniel
sbcl (which is cmucl fork) does support arm32 and arm64 architectures (fwiw arm32 doesn't have threads - alternatives are ecl and ccl (probably abcl too) which both support threads on that platform)
12:46:02
jackdaniel
soyeomul^bionic: here are supported platforms: https://www.common-lisp.net/project/cmucl/platforms
13:18:31
jackdaniel
soyeomul^bionic: mentioned compilers all implement same standard (Common Lisp). If this server is made with CMUCL, then it is very likely it doesn't require much work to port it to other implementations too
13:20:09
soyeomul^bionic
jackdaniel: i get understand your words, thanks, so i try with SBCL? SBCL have ARM64.
13:23:43
jackdaniel
soyeomul^bionic: yes, please try sbcl. it is the most similar to cmucl (since it is its fork)
14:46:06
phoe
Like, I want to find the PRINT-OBJECT method that gets called if I pass it arguments :FOO *STANDARD-OUTPUT*.
14:47:23
jackdaniel
phoe: compute-applicable-methods-using-classes or compute-effective-method-function
15:20:47
phoe
https://cdn.discordapp.com/attachments/297478350145060875/540552002665578528/Zrzut_ekranu_z_2019-01-31_16-20-35.png
15:35:02
dlowe
phoe: it looks like you're keeping the local nicknames as strings, but it might be better to store them as symbols, maybe even in an internal package
15:41:17
phoe
ADD-PACKAGE-LOCAL-NICKNAME, REMOVE-PACKAGE-LOCAL-NICKNAME, PACKAGE-LOCAL-NICKNAMES and PACKAGE-LOCALLY-NICKNAMED-BY-LIST were copied from SBCL and adapted to CCL's package system.
15:44:21
dlowe
The image I'm running right now has 160 packages, if each of them had 15 local nicknames, that would be 2400 symbols
15:45:21
phoe
I'd assume nickname "F" in ten different packages would map to one internal symbol named "F"
15:47:02
dlowe
I might try to run ansi-tests for the package section to make sure you didn't break anything.
15:49:13
phoe
CCL is a code soup with a lot of spaghetti - refactoring and documenting it in general would be a lot of joy for multiple people
15:56:07
shka__
as i said, it is somewhat out of scope of this task, but i think it would be acceptable to go ahead with this addition anyway
15:58:09
phoe
For now - if anyone is able to follow the bootstrapping steps I have written, please do it