Edi Weitz edi@agharta.de writes:
I fixed it by having the %foreign-funcall expansion call get-foreign-funcallable at run-time and also at macroexpansion time. Let me know if you have a better idea.
Yeah, an oversight of mine - thanks for fixing that. I can't come up with a better idea right now but I'll keep it in mind.
I wrapped get-foreign-funcallable in a load-time-value. I remember James suggesting this when he first looked at your patch. I have no idea why I didn't try this first.