14:36:16beachWhy does SICL have a (SETF ACCESSOR-METHOD-SLOT-DEFINITION) function? The MOP doesn't mention any slot writer as far as I can tell.
14:39:00beachOK, I think I figured out how to avoid satiation altogether. Therefore, this idea of having the :TYPE slot option influence the method specializer is probably no longer interesting, at least not for the initial reason I thought about it.
14:42:12beachThere seems to be around 80 or so functions (generic or not) in the MOP. SICL defines a few more, of course, and there are the ones from the Common Lisp HyperSpec, like make-instance, initialize-instance, shared-initialize, etc. etc.
14:42:21beachHow many of those are slot accessors?
14:46:15beachI think I need to go thorough each and every one of those to see in which environment it ends up, which other functions call it, and which other functions are called by it.
14:58:08shka_so you could build queries like: please give me all X where X is a class that happens to be superclass of Y where Y is something that beach created
14:58:38shka_not sure how it is useful it would be
14:58:47beachYes, I see. Interesting idea. It might be quite relevant for CLOSOS.
17:58:31jcowanThere's a reference manual for Masterscope in http://www.softwarepreservation.org/projects/LISP/interlisp-d/3100186-Interlisp_Oct83.pdf on physical pages 351-372. Note that Interlisp did not have classes, but this should give you an idea of what can be done. (Warning, huge 800+ page scanned and unsearchable PDF, may be very slow to load in your PDF viewer.)
18:03:32jcowanNote that Masterscope worked entirely by reflection on the contents of memory without referring to any files. This may not be feasible in a modern CL system.