freenode/#clasp - IRC Chatlog
Search
20:08:33
attila_lendvai
Bike: I'm only talking about turning off saving literal arrays and instances
20:09:45
drmeister
I'm not sure that there is a problem. The fasl files that we generate now come from compiling lisp source code. I don't see how you could run into this problem.
20:09:57
attila_lendvai
Bike: to send an error/warning for stuff like: (defun foo () #.*some-clos-instance-pointing-into-a-large-and-complex-graph*)
20:11:08
Bike
and i don't really get the point, i mean, if you're throwing a literal object into a fasl you know what you're doing enough to write a make-load-form method and all
20:11:24
attila_lendvai
I did run into sbcl throwing an error when I tried to save a literal instance a few times, and it was always due to some confusion on in some of my macros
20:14:28
attila_lendvai
oh, and now that I recall, it was mostly when trying to save lambda's. clos instances have the m-l-f with a sane error message when unimplemented. so my concern is mostly with arrays forming a graph, but... maybe I'm overblowing it, and people just need to learn what they are doing.
20:31:55
drmeister
If we just focus on the build system for a moment. (1) We keep track of classes that are created during compiling the cclasp source code.
20:32:50
drmeister
(2) We generate a bunch of RUNALL commands that are run before anything else and create all of those classes.
20:35:57
Bike
also have to make sure the make-load-form methods for ast classes are setup right, i guess.
20:48:37
Bike
Not really. make-load-form has specified behavior on classes. We'd have to do something magical.
20:52:20
drmeister
Yes, IIRC rawRef_() returns a reference to the contained pointer and raw_() just returns the contained pointer.
21:08:38
drmeister
I'm having to compile things over and over and over again to bring the new joint-tree code online.