On Mon, Jul 28, 2014 at 10:23 AM, Raoul Duke <[email protected]> wrote:
> i should think any real systems language would have to have *very* > strong alternatives / answers when regular programmers walk up and > say, "so how do i log the call stack?" because that is what we do > pragmatically to get things done. Raoul: At the risk of being obnoxious, I'm going to go out on a limb and guess that I've been shipping software products since before you were born. In all that time, I have never *once* logged a call stack, so I'm going to be hard to convince that it's an absolute necessity. In any case, if you *do* need to do it, walking the call stack is a runtime function. It can be done as an "arm's length" operation. The problem isn't so much acquiring a dump of the current stack as it is exposing the stack to mutation. shap
_______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
