Simon Rozman 2680cdb3fd Upgrade win_runtime_error and ws_runtime_error to include error message ...

Upper levels usually just catch std::exception and display what()
message to the user. Rather than requiring typed exception catching and
per-type user message synthesis, it's easier for upper levels if we
stuff the Windows/Winsock2 formatted error message at the end of the
string returned by what() and leave the catch (std::exception&) do the
magic.

Signed-off-by: Simon Rozman <simon@rozman.si>

2023-10-03 15:18:25 +02:00

..

WinStd

Upgrade win_runtime_error and ws_runtime_error to include error message

2023-10-03 15:18:25 +02:00