Hi,

I found that the behavior of ExceptionHandler.FilterEnd is a bit
surprising: while TryEnd and HandlerEnd are exclusive (point to the next
instruction after the last); the FilterEnd in Cecil seems to be
inclusive (pointing to the "endfilter" instruction).
Also, it looks like FilterEnd is a Cecil invention - the metadata only
contains the filter start.

So maybe you should just get rid of that property completely? If it was
implemented consistently with TryEnd/HandlerEnd (exclusive end
coordinate), it would always return the same value as HandlerStart...

By the way, I found this when trying ILSpy on
MS.Internal.Threading.TryCatchWhen (in WindowsBase, part of WPF).
Apparently that's the only place in the whole .NET framework that uses
an exception filter...

Daniel

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to