SBCL Internals
The pages on this CLiki-driven site can be edited by anybody at any time. No warranty of any kind can therefore be made; any implied warranties of merchantability or fitness for a particular purpose are expressly disclaimed

Nikodemus thinks having an exported interface would be good. TODO? Internally something fwrapper-like exists as ENCAPSULATE &co in src/code/fdefinition.lisp.

Fwrapper

An exported fwrapper interface would be nice. Allegro's is worth looking at, but not adopting as such:

Effect of fwrapping on function identity is not specified.
Effect of redefining fwrapped functions is not specified.
FWRAP-SORT interface is ugly.
DEF-FWRAPPER seems a tad too concerned with efficiency: CALL-NEXT-FUNCTION semantics should be more similar to CALL-NEXT-METHOD.
No way to recover fwrapper function objects.

FWRAP could be preserve identity if it can be written in terms of breakpoints as used by TRACE. If not, the exact semantics need thinking about: does replacing an existing inner wrapper of an anonymous function return a new copy of the frwapper chain with one link replaced, or does it modify the exiting one?

This page is linked from: TRACE

CLiki pages can be edited by anyone at any time. Imagine a fearsomely comprehensive disclaimer of liability. Now fear, comprehensively