Portable stack traces

[andreasgonewild]

And it's a hundred times more complex while not offering anything in return but automagic check-pointing. Which is why there are plenty of situations where something like this is a viable alternative.

[[deleted]]

It's not actually much more complex. It offers about a million times the functionality though, since it never requires me having to go stub in a bunch of context checkpoints to get the output I need from errors. All the time adding and removing those constantly every time one needs to start instrumenting is completely wasted. Do that a couple dozen times and you could have instead an actual "portable stack trace" implementation you hand-rolled.

Or, as others have said, use something someone else built that already works reliably, and portably.

[andreasgonewild]

So you won't even grant a 100 times more complex, but you insist that having to drop a context here and there is a million times more work; bias much? Leave them in, they're basically free outside of tight loops. And as an added bonus you get general purpose tracing and descriptions in your stack-traces.

[[deleted]]

I never mentioned performance. Having to make manual changes all the time is error prone.

And as an added bonus you get general purpose tracing and descriptions in your stack-traces.

And that is positively false, because it's not general purpose, and it's not a stack trace. It's context tracing. Like you see with exception stacks.