freenode/#mezzano - IRC Chatlog
Search
18:30:36
froggey
elderK: great, portable code should work without issues. let me know if you run into problems
18:32:37
elderK
froggey: NP :) I may or may not rewrite this again, based on new feedback from #lisp.
18:32:49
elderK
froggey: I was wondering what the color-coded bars at the top of the screen mean? And the same for hte Memory viewer.
18:33:45
elderK
froggey: Also, I've been meaning to talk to you about Lisp implementation and stuff. And how you got started, and if you had any suggestions for how I could get started down that road :)
18:49:48
Grumblefumb
froggey: I often have freezes when resizing a window or starting an app. Is that the jit compiler?
18:52:00
elderK
Grumblefumb: Me too. Earlier today while ASDF was doing something, I thought it had hung
18:54:00
froggey
slowness when starting apps might just be it paging the code in from disk for the first time
19:06:06
elderK
I was wondering like, are there any... knobs or ... statistics available for us to determine places that might benefit from optimizatoin?
19:06:26
elderK
Also - and I haven't yet studied the docs in detail -but is there like "A Newcomers Map to Mezzano"
19:11:42
froggey
compilation is slow primarily because the register allocator is slow & stupid. it's surprisingly difficult to write one that's half-decent
19:12:47
froggey
there are a few places where statistics are gathered, but the profiler is the primary mechanism I use
19:14:05
froggey
I'm not sure what a newcomers map would cover, when I have to deal with looking through a large project I start by looking at the bits I'm interested in & what they touch
19:18:11
Grumblefumb
One tip might be to start the filer and look into Source instead of trying to make sense of the github repo. :)
19:19:32
Grumblefumb
There it is: med, mcclim, alexa, everything that is on the system. I should have tried that firt
19:22:12
elderK
And I connect to Mezzano say, with SlimV - It's going to need to know how to find the source for Mezzano
19:23:55
froggey
could be. check the lights in the top-left, the green light means there's a disk read in progress, which generally indicates paging
19:24:02
Grumblefumb
.oO(undefined function MED:SLIME-COMMAND... well, it was worth a quick shot. :) )
19:27:50
elderK
froggey: :) So, to someone wanting to get into the compiler-world wrt Lisp, any suggestions on books, resources, projects to look into, etc?
19:31:27
froggey
nothing specific, I don't really keep track. I have appel's modern compiler implementation (the tiger book)
19:32:08
elderK
I own things like the dragon book and stuff - but I was wondering how much is transferable from "compiling mainstream stuff" to "compiling Lisp or Scheme"
19:34:33
elderK
:) I guess I'll have to finally work through Dragon Book, LiSP and such - and do all of the exercizes.
19:35:11
elderK
There are a lot of things that interest me. Like, I wonder if CL has some "basic core lexer and tokenizer and stuff", so that it can understand "basic CL code". But then, has a layer on top of that, that allows those things to be redefined (reader macros, etc.)
19:37:05
froggey
the reader algorithm, how symbols are processed & reader macros are dispatched, is described by the standard
19:37:36
elderK
The control and data flow analysis must be interesting, too, if you like, want to avoid dynamic allocation as much as possible. Say, if you see that a vector is only used in the function and doesn't escape, to allocate it on the stack if possible.
19:40:17
froggey
I haven't really bothered with escape analysis for stack allocation, it relies on dynamic-extent declarations to stack allocate things
19:40:38
Grumblefumb
Is there a shutdown command? :) Taking a snapshot is denied (running read-only)