Files
epics-base/modules/libcom/src
Érico Nogueira 8045770751 libCom: don't use std::unexpected in epicsThread.
Besides being deprecated in C++11 and removed in C++17, the intended use
case for this was always wrong, since std::unexpected() is called by the
C++ runtime when a function throws an exception that was not specified
in its "dynamic exception specification", which is different from an
exception thrown by user code which wasn't caught [1,2]. Using abort()
keeps the same behavior, but with the intended semantics.

We don't use std::abort() to simplify backwards compatibility.

[1] https://github.com/epics-base/epics-base/issues/343
[2] https://en.cppreference.com/w/cpp/error/unexpected
2024-09-09 07:27:32 -07:00
..
2023-12-22 10:26:28 -08:00
2021-08-29 07:27:50 -07:00
2023-12-14 16:42:10 -06:00
2021-08-29 07:27:50 -07:00
2021-08-29 07:27:50 -07:00
2024-06-11 11:14:07 -07:00
2023-12-22 10:26:28 -08:00
2024-06-11 13:52:03 -07:00
2023-11-07 15:53:22 -08:00
2021-08-29 07:27:50 -07:00
2023-03-10 10:57:35 +00:00
2022-01-28 11:23:16 -08:00
2018-06-19 11:25:46 +02:00