[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Eval, tail calls, (current-module), and backward compatibility
From: |
Andy Wingo |
Subject: |
Re: Eval, tail calls, (current-module), and backward compatibility |
Date: |
Mon, 23 Jan 2012 11:41:15 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux) |
On Tue 17 Jan 2012 04:28, Mark H Weaver <address@hidden> writes:
> Ideally, I think that `eval' should set (current-module) during
> expansion, but _not_ during evaluation. Then it can be properly tail
> recursive. However, some code out there might depend on the existing
> behavior, so I guess we can't change this, at least not in 2.0.
> Bummer.
Dunno. There are lots of instances of (current-module) in our current
code, and in code from lots of external projects. I think if we changed
it, it would break a lot of stuff, subtly.
Andy
--
http://wingolog.org/
- Re: Eval, tail calls, (current-module), and backward compatibility, (continued)
- Re: Eval, tail calls, (current-module), and backward compatibility, Ludovic Courtès, 2012/01/18
- Re: Eval, tail calls, (current-module), and backward compatibility, Andy Wingo, 2012/01/18
- Re: Eval, tail calls, (current-module), and backward compatibility, Ludovic Courtès, 2012/01/18
- Re: Eval, tail calls, (current-module), and backward compatibility, Andy Wingo, 2012/01/18
- Re: Eval, tail calls, (current-module), and backward compatibility, Ludovic Courtès, 2012/01/18
- Re: Eval, tail calls, (current-module), and backward compatibility, Andy Wingo, 2012/01/18
Re: Eval, tail calls, (current-module), and backward compatibility, David Kastrup, 2012/01/21
- Re: Eval, tail calls, (current-module), and backward compatibility, Mark H Weaver, 2012/01/21
- Re: Eval, tail calls, (current-module), and backward compatibility, David Kastrup, 2012/01/21
- Re: Eval, tail calls, (current-module), and backward compatibility, Mark H Weaver, 2012/01/21
Re: Eval, tail calls, (current-module), and backward compatibility,
Andy Wingo <=