| commit | 2f48e1497c757fe4b64aeca0ccc9507b9f1c1e2e | |
| author | Douglas Katzman <dougk@google.com> | |
| Sun, 30 Nov 2014 22:05:00 +0000 (30 17:05 -0500) | ||
| committer | Douglas Katzman <dougk@google.com> | |
| Sun, 30 Nov 2014 22:09:36 +0000 (30 17:09 -0500) | ||
| tree | 8a45ca6e6947cb0f4959742b6944d399b09b6189 | treesnapshot (tar.gz zip) |
| parent | 17294c2983d9f37dc9edc815364c0ccc2afc6a9c | commitdiff |
Simplify WALK-METHOD-LAMBDA and consumers thereof.
The earliest PCL releases had many different ways to expose CALL-NEXT-METHOD
(named ADD-LEXICAL-FUNCTIONS-TO-OPTIMIZED-n for n=1..6) depending on whether
it was ever an operand to FUNCTION in a particular method and/or whether the
method always, sometimes, or never passed arguments to CALL-NEXT-METHOD.
(And a local macro binding was generally favored over a local function)
In contrast, the 'closurep' flag served no purpose in SBCL, and by providing
NEXT-METHOD-P gratuitously, there is no need to pre-scan for uses of it.
The earliest PCL releases had many different ways to expose CALL-NEXT-METHOD
(named ADD-LEXICAL-FUNCTIONS-TO-OPTIMIZED-n for n=1..6) depending on whether
it was ever an operand to FUNCTION in a particular method and/or whether the
method always, sometimes, or never passed arguments to CALL-NEXT-METHOD.
(And a local macro binding was generally favored over a local function)
In contrast, the 'closurep' flag served no purpose in SBCL, and by providing
NEXT-METHOD-P gratuitously, there is no need to pre-scan for uses of it.
| src/pcl/boot.lisp | diffblobblamehistory |