From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-03-25 13:22:26
----- Original Message -----
From: "Douglas Gregor" <gregod_at_[hidden]>
> Note a few important things: there is no instantiation stack
When debugging metaprograms, some sort of instantiation stack is often
the only thing that saves me.
IMO, the way to deal with that particular issue is:
1. Start with the deepest part of the stack (where the error occurred)
2. Show the shallowest part of the stack next
3. Show the rest of the stack last
4. Use some kind of "error folding" in the editor/IDE so most of the
stack is invisible until you click on a widget (or equivalent).
OTOH, it might make sense for your error mechanism to be able to cut off
instantiation details deeper than a certain level.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk