Closed ilzxc closed 10 years ago
Here's a slightly augmented version of the trouble case:
<pre><code>
----------begin_max5_patcher----------
618.3ocqU1zbaBCDF9L9WwN5j8TpAbnj3LiO1N8R6za8fsmLxvZGkBRdDBan
Yx+8pOfXbSbhmL9hfcY0qd0pGfGG3QVIpwRBbKLG77dbfmmMkIgWarGofVml
SKskQREEEHWQ7cOSg0Ja9uJkBIv3vOn0vuY7LwdenTIo7MHP4k6Q4scSZKUk
dOiu4NIlpbK9UgiC8aGmDEaunCfksSYsfqJY+EMUGMQ+XWZdUAimiJq2hZSx
xrNRr5gOGES5I.mVXEf7cLeGpXoT3mXE9rsjXodqQULAum0Rhux5solwv1gm
Ml1AhJUmE570Z4lU13wglDOMXfYv+L6whwYrxs4zlWzkCJZBnYY5aWPxoEqx
nCg409PyRenF9Dz.iVP7WvM0kyJUlMPrO7kklbbrTgYAqq3oA6Yp6CnRIso7
Xwzxn0pccFB0ymC5MqQd8cQ56fQcqwA8B1iLYlN9UEqSCs+NHhSBkVhNcbto
y1KHwMurl9qyzttSNiiohJtsEk7dLVzMNT65qsQgwuOk4NfUMaQmPDR+i+2D
.mdI3uarNMI4UAPCajJxERW0g8KROqShpQeHvDq2JGmJxPSgmhNmctz4LvbY
HXPTXzawnytjL5rKBiNCNkaGBOuCGcZB9n4eHe+I+wH7DGfeyDGfO4C.3eqJ
O+Wzz+f5OzeTzYC9QgWLx+pnKJ3OoG3aKw1d+ueBZatl7G+1PonRl10j51lv
gUJSefx318QuhldTM2yxxPd++Vn+ZOcUNZadguvczsa2gxxVIsNQ+V4Ct8sE
FH5iBWn8ffHwcrt5cEPkZTQoarUR24PcRLYfYcdZv+vYpkAJ
-----------end_max5_patcher-----------
</code></pre>
fixed---this was subtle. The part of the code that was building up the lexical environment for the lambda function was evaluating the arguments that were to be bound in that lexical environment in the context of the new environment, not the old. This may fix some other weird behavior that we've seen...
This is difficult to explain. Please see attached patcher: