Error stack

[Brendan Eich]

Mark S. Miller wrote:
> I'm not yet arguing that or the opposite, rather, I'm confused about
> what "non-strict-only" means in this context. Actual stacks consist of
> a mixture of strict and non-strict activations.

This isn't so in personal projects or even all-homegrown products or 
shared projects that eschew "use strict", as Charles wrote.

>   How would the proposed API deal with that?

Eliding strict frames' arguments, Charles wrote.

I objected that this makes any such stack trace API hard to use in the 
large, compared to an information-leaking string-valued .stack approach.

/be