You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
For MSVC no exceptions builds do not use _CPPUNWINDÂ #48
SEH is intrinsic to Windows, thus your future customers, Windows teams using that /kernel switch will very likely expect nonstd to raise one or few Structured Exception.
Thanks ...
ps: since my readme.md over there is atrocious. I need to simplify it. I don't understand it myself.
Will need some time to further the exceptional behavior. Likely want to make it configurable under Windows to either use assert() or SEH.
Well, the "fail fast" movement is certainly raising ... And any of the three (compilers) is here to oblige ...
ps: the side issue -- is this not a great real-life example of why sometimes single include file policy fails :) I mean no disrespect but now you need to travel around repositories and change things, instead of having one common header (single place) where one could change this kind of top-level issues. I am going back to the "single top-level set of headers" model. Ugh.
Activity
martinmoene commentedon Nov 15, 2020
Replace
with
Plan:
Replace _CPPUNWIND with _HAS_EXCEPTIONS(#27, thanks @DBJDBJ)
Replace _CPPUNWIND with _HAS_EXCEPTIONS (thanks @DBJDBJ)
Replace _CPPUNWIND with _HAS_EXCEPTIONS (thanks @DBJDBJ)
Replace _CPPUNWIND with _HAS_EXCEPTIONS (thanks @DBJDBJ)
Replace _CPPUNWIND with _HAS_EXCEPTIONS (thanks @DBJDBJ)
Replace _CPPUNWIND with _HAS_EXCEPTIONS (thanks @DBJDBJ)
Replace _CPPUNWIND with _HAS_EXCEPTIONS (thanks @DBJDBJ)
Replace _CPPUNWIND with _HAS_EXCEPTIONS (thanks @DBJDBJ)
Replace _CPPUNWIND with _HAS_EXCEPTIONS (thanks @DBJDBJ)
DBJDBJ commentedon Nov 15, 2020
Thanks, @martinmoene , great :)
Over here is my unfinished result on the subject of MS STL and
/kernel.Kind regards
martinmoene commentedon Nov 15, 2020
Thanks
Will need some time to further the exceptional behaviour. Likely want to make it configurable under Windows to either use
assert()or SEH.Kind regards
DBJDBJ commentedon Nov 15, 2020
Good, you made that decision,
SEH is intrinsic to Windows, thus your future customers, Windows teams using that
/kernelswitch will very likely expectnonstdto raise one or few Structured Exception.Thanks ...
ps: since my
readme.mdover there is atrocious. I need to simplify it. I don't understand it myself.Replace _CPPUNWIND with _HAS_EXCEPTIONS(#27, thanks @DBJDBJ)
Replace _CPPUNWIND with _HAS_EXCEPTIONS(#27, thanks @DBJDBJ)
2 remaining items
Replace _CPPUNWIND with _HAS_EXCEPTIONS (thanks @DBJDBJ)
Replace _CPPUNWIND with _HAS_EXCEPTIONS (thanks @DBJDBJ)
Replace _CPPUNWIND with _HAS_EXCEPTIONS (thanks @DBJDBJ)
Replace _CPPUNWIND with _HAS_EXCEPTIONS (thanks @DBJDBJ)
Replace _CPPUNWIND with _HAS_EXCEPTIONS (thanks @DBJDBJ)
Replace _CPPUNWIND with _HAS_EXCEPTIONS (thanks @DBJDBJ)
Replace _CPPUNWIND with _HAS_EXCEPTIONS(#27, thanks @DBJDBJ)
Replace _CPPUNWIND with _HAS_EXCEPTIONS (thanks @DBJDBJ)
Replace _CPPUNWIND with _HAS_EXCEPTIONS (thanks @DBJDBJ)
Replace _CPPUNWIND with _HAS_EXCEPTIONS (thanks @DBJDBJ)
Replace _CPPUNWIND with _HAS_EXCEPTIONS (thanks @DBJDBJ)
Replace _CPPUNWIND with _HAS_EXCEPTIONS (thanks @DBJDBJ)
Replace _CPPUNWIND with _HAS_EXCEPTIONS (thanks @DBJDBJ)
Replace _CPPUNWIND with _HAS_EXCEPTIONS (thanks @DBJDBJ)
DBJDBJ commentedon Nov 29, 2020
Well, the "fail fast" movement is certainly raising ... And any of the three (compilers) is here to oblige ...
ps: the side issue -- is this not a great real-life example of why sometimes single include file policy fails :) I mean no disrespect but now you need to travel around repositories and change things, instead of having one common header (single place) where one could change this kind of top-level issues. I am going back to the "single top-level set of headers" model. Ugh.