RFC: <excpt.h>: __try1/__except1 are broken; are they worth fixing?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Guys,

Further reviewing Cesar's clone of our original CVS:
https://sourceforge.net/u/cstrauss/mingwrt/ci/56e6189f267527e4dd710d55a16de39f7bf21c4a/

I stumbled upon:
https://sourceforge.net/p/mingw/bugs/1328/

IMO, this bug report was inappropriately closed, as invalid.  I've
reopened it, accordingly, because, as may be seen from the extensive
analysis which I've appended thereto, this commit:
https://sourceforge.net/u/cstrauss/mingwrt/ci/3eac8de7de5be34a9b58918ae8500697a7ddc1c4/

does nothing even remotely useful to resolve the issue; in fact the
entire __try1/__except1 implementation is so utterly TARFUBAR, that I
wonder if it is worth expending any effort on fixing it, or should it
simply be allowed to disappear without trace?

Thoughts?

- -- 
Regards,
Keith.

Public key available from keys.gnupg.net
Key fingerprint: C19E C018 1547 DE50 E1D4 8F53 C0AD 36C6 347E 5A3F
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)

iQIcBAEBAgAGBQJXaE01AAoJEMCtNsY0flo/29YQALi6VnW5WxyiyV77+v/vp5XZ
Y4gI2TP2L65tC9+0XNCIGoPUxctEa3SIA8tOXU5xTizIBoTVgofAMwfBwvpxMFNK
msel0LANyc+bRRiYQlequYfHEq8VRWoae+Yw28vdPsNCiC0MDdmpGaxNgAwVnteQ
ztTji+M3SKxCOE8XBI/mjQ7K22IXD+YF70Hjs/KxEV6ESc/0vbFrXcJRgr1o5Mdt
J3/VLW35rwn9Wxz/aQNvOpsF1YcY/jfQCpvNCO/75vq97lpjIJWcqecas172Manp
fg9RYG0c8y33VgJCPqQvFvb9Ja2+/hps0myzedv4OgvfZ6wMNj5c4Bg5AKnl1KtP
/5+p4hI4cJ6+ZleQgq7gaiXwMkQrt/zm/eF/bqT5VY/vdpnwC2dZviyjL50AZ5LU
URMlL6zt5GV8BO5OVlOph/eZzK/kWYI9aG5vn5fxfnbD0jHFtFGeQ4wih+gq8VQF
Z28XNc1KFxpzrA6JkR4UrEtD+hboxBQWNqmbZu+qPK9W0CDQ1yPhpnBmWY0e5PsY
hJ6uAMZW2LB015f1fX2QZGFe0XkjTilS8SGYKIT4kp6gujolWyucAuqHVemh5FYt
GHHGldmMh0b8Ds5E15kcnUDH/6eRY9m7j7AaFrI6NDc9PhbTTNOZURov9Lg5DuvK
KJNE54TjznPYQwRrnwEZ
=NL9z
-----END PGP SIGNATURE-----

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports. http://sdm.link/zohomanageengine