> But that begs the question: why do you want this, given that you agree that > walking the stack raises ambient authority issues?
i'm hopefully missing the way in which BitC features make up for not being able to walk the stack for my logging messages. e.g. if there's a way for the compiler to insert the debug stack strings fine. (because i need to get this stuff fixed and shipped yesterday, and the easiest way to figure out why Somebody Else's Code is breaking is to just log the hell out of it sometimes. especially if it is a big service, i can't just have breakpoints and stop things and peek around, things will time out, etc. 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. like, that should be in the faq with full code snippets.) _______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
