but you should realize that like you cant necessarily assume that all of the pointers in the optree are valid post compilation.

The optree traversal code already exists in D::S, I'm not adding to or changing it, only trying to handle the exceptions that can arise from it.

be aware that data pointed to by the optree may not be allocated via SV allocation

I was aware the idea was a bit hookey and wouldn't handle some situations, only the preponderance of those I had encountered.

I also knew there is a better way, try{ } catch { }, but I couldn't get that to work. Turns out I was missing something simple and it is now working, so I can ditch the low-tide mark idea.

Now all I need is to figure out the gcc/posix equivalent of MSC __try{} __except()?