freenode/#clasp - IRC Chatlog
Search
21:03:15
drmeister
I'm confused about something -- FuncallableInstance_O vs CompiledDispatchFunction_O
21:03:52
drmeister
I 'evolved' the two classes to shoehorn fastgf into a system supporting ECL dispatch.
21:05:13
drmeister
Now that fastgf is taking over - things are different. What is the role of these two classes or (more likely) if CompiledDispatchFunction_O is torn out - how does FuncallableInstance_O take up the slack?
21:05:50
drmeister
FuncallableInstance_O inherits from Function_O - which is the base class of all function objects.
21:06:24
drmeister
Function_O has a 'entry' slot - that is a function pointer of the type that can be generally called within Clasp.
21:08:38
drmeister
Further, I think that set-funcallable-instance-function sets the 'entry' of a FuncallableInstance_O to the 'entry' of a Function_O object.
21:10:00
drmeister
Further, I'm starting to think I can get rid of the special functions for JITting dispatchers - I think they are now no different than regular JITted functions.
21:28:37
Bike
in a normal implementation you can compute-discriminating-function, get a regular function, and put that as the funcallable instance function
22:25:33
drmeister
Basic question - what is a funcallable-instance? Are they used for anything but generic functions?
22:26:07
Bike
also, to answer your question from before i left, fixing the specializer profiles fixed the problem
22:30:14
specbot
funcallable-standard-instance-access: http://metamodular.com/CLOS-MOP/funcallable-standard-instance-access.html
22:32:09
drmeister
These new discriminator functions simplify things a lot. I can get rid of special code for JITting discriminator functions.
22:32:25
stassats
the more pertinent funcallable-instance quality is actually the ability to have different classes