Jason Orendorff
Jason Orendorff
> Just to point out that the stack at the time `eval` is called does not help us with the problem address by naming the buffer. Completely agreed: it does...
@samth and @jorendorff say: Wait until a LinkSet including this module gets linked and committed. I'll try implementing this.
I'm all for fun, but it's really hard for a method to be both (a) an extension point where users can plug in whatever code they want and (b) well-behaved...
Regarding question 3, I think direct eval could reasonably use the caller's loader, and indirect eval should basically be System.eval.bind(System).
Changed my mind. Direct `eval` should _NOT_ call the `translate` hook of the caller's loader: - A direct call to `eval` in compiled source code should have the same meaning...
I think we have agreement on eval(), but we need an answer for Function().
@dherman says H, I, J, K, L, and N should be fine. Ambivalent about M, but really wants to reject G. Fine with A-F still being errors.
I think we should reject H-N. None of those are useful things to say.
I'd like to understand this better. In @jrburke's case, where the module wants to know its own name, why is the module author in the dark about what module he...
> _From looking at the Loaders spec, it seems that this info is there, just no way to access it at present._ Oddly enough, it's _not_ there; modules really don't...