dereferencing null

[David Nadlinger]

On Thursday, 8 March 2012 at 22:20:10 UTC, Walter Bright wrote:
> I agree, it really is very flexible and useful. The downside is 
> that it leaves significant overhead in functions that are 
> exception-aware, even if they never throw or unwind.

This problem is avoided by the switch to the table-based 
implementation on x86_64, though, while the flexibility, as far 
as I know, still remains.

> And you're right about the documentation. It's incredibly 
> obtuse, probably the worst I've ever seen.

Yes – I love how everybody (including me) working on SEH code 
seems to end up reverse-engineering at least certain parts of it 
on their own.

David