freenode/#lisp - IRC Chatlog
Search
4:22:37
beach
uncommon_lisp: That's very kind of you. I'll work on it a bit more and then I'll submit it for remarks here. I know flip214 is expecting more material from me before he is able to comment any further.
4:23:25
beach
He is right that it was very sketchy, and I need to work out the details. And there turn out to be many such details to work out.
4:28:37
Jachy
Is the spec for a particular GC implementation or for being able to integrate/swap different GCs?
4:29:12
beach
Jachy: That would be very hard to do. The GC is intimately tied to other implementation aspects of the system.
4:30:18
beach
Jachy: The book is absolutely horrible when it comes to the writing itself, but it does contain a fairly complete description of must existing techniques.
4:31:03
Jachy
I've got a digital copy of the garbage collection handbook if that's the one you're referring to though I have barely scratched the surface in the past.
4:31:25
Jachy
I'm just thinking of the JVM with its several GC implementations (and a few proprietary ones like Azul's) has been an advantage.
4:31:57
pillton
When is the 2016 edition coming out in dead tree form? The website has been saying soon for ages. I emailed the publisher and I got no reply.
4:32:29
beach
Jachy: Just keep in mind that, if you read a section and do not understand it, it may not be your fault. It could very well be the bad writing.
4:33:05
uncommon_lisp
I was going to buy that book but now I'm not so sure I want to waste money on bad writing
4:34:12
uncommon_lisp
I could request that you write several essays and compile them into a book for me, and then post it here.
4:35:09
beach
Heh. On GC, specifically? Sure, but I would manly just rehash what the others have already written.
4:36:11
beach
There might be some value to that, because I think of myself as a better writer than Jones. Maybe not better than Paul Wilson, though.
4:37:18
uncommon_lisp
If you do write a comprehensive paper on it (not in a scholarly, verbose fashion, but in the style of K&R or Maurice J. Bach's design of unix), I'd read it for sure
4:40:42
uncommon_lisp
Btw, I missed the conversation regarding the gc (what it's for (the software package I mean)) - are you writing the gc and everything in CL?
4:40:44
Jachy
Wilson's paper seems very familiar, I suspect I read it before sometime in the last 4-6 years but it's not in my finished folder..
4:42:28
beach
uncommon_lisp: I am planning to write as much as possible in Common Lisp. For now, I am just writing a detailed specification of the GC I am planning for SICL.
4:43:06
Jachy
It is dated in that no mention of real time GC, but the Handbook only goes over that in the final chapter. Doesn't seem like there's that much interest in real time systems in the broader environment anyway.
4:51:15
uncommon_lisp
The climacs editor in particular was something I was really interested in back when I was trying my best to avoid emacs.
7:02:58
flip214
beach: just prove that your GC is correct, no need for debugging or even writing it then ;P
11:04:19
jmercouris
jackdaniel: outside of mcclim, what is, in your opinion the best cross-platform GUI?
11:04:36
jackdaniel
there is a separate system (in the same tar shipped by quicklisp) which gives you many useful widgets
11:09:07
jackdaniel
everything is a huge challenge given person in question needs to learn the basics of the tool in question
11:10:22
jmercouris
I had to make modifications to the actual source of EQL to get it to work with different versions of QT
11:10:33
jmercouris
and platform specific differences for how one distributes a binary are also a huge challenge
11:10:45
jmercouris
normally when working in the QT environment, QT provides all of that tooling for you
11:11:00
jmercouris
but when you have to use unupdated insufficient command line tools, it isn't a good time
11:11:15
jmercouris
it would be like trying to compile and distribute an xcode project entirely on the command line, its totally possible, but its totally not made easy for you
11:11:37
jackdaniel
I don't understand what you are saying, but that's most likely lack of knowledge on my site. I'll be back later
11:24:44
jmercouris
jackdaniel: https://github.com/next-browser/next/tree/07778d29925be3c936d9b1df5060abda7d68abef/next
11:25:09
jmercouris
for the record, it would not even install on OSX when I started, that is far later on, the earlier instructions are even worse
11:25:34
jackdaniel
but what do I know ,) either way, OSX isn't very appealing platform, I believe you
11:28:06
jackdaniel
not against me, I have no interest (sorry about that), how deep into craziness you've digged on OSC ;p
11:28:27
flip214
DEFTYPE allows to do parametric types, like (DEFTYPE UINT (size) `(INTEGER 0 ,(1- (expt 2 size)))). but such types can't be used in DEFMETHOD, right?
11:29:38
jackdaniel
what you could do is to detect type during dispatch and construct object of a specific class (to dispatch on it) – look at filtered-functions for such possibility
12:01:29
jmercouris
aha, here it is: https://www.common-lisp.net/project/slime/doc/html/Communication-style.html
14:58:48
beach
GAH, working out the details of how the SICL garbage collectors will work is both painful and totally necessary. I am grateful to flip214 for not being content with my sketchy description of it. It turns out there are tons of little details to hash out. A few bitmaps here and there, the order between promotion and compaction in the nursery, how promotion works exactly, etc. etc.
15:01:00
beach
Xof: You are off the hook (for now). I need to determine a lot more details before I will ask you again to review it.
16:03:23
hjudt
i have a slime usability question. when i have a macro like (with-stuff (bindings) object) and object is in the same line as the last binding, emacs highlights object in red color. why does it do that? if i put it in the next line, it doesn't get highlighted in red.
16:07:13
beach
hjudt: It doesn't happen to me. At least not in every situation similar to what you describe.
16:11:17
Xof
if you are closing something that was opened on a previous line, it's unconventional to have more stuff on the line that closes