Hi Boris,
> Wouldn't it make sense to move with_libc into the critical functions
> that need it themselves? Or to create wrappers for them in the include
> files included by the components (socket.h etc.), similar to how posix
> just transparently wraps main() in with_libc? This way the programmer
Well, what it does now it that the program just crashes with an
"uncaught exception".
Catching all exceptions inside becomes very hairy though, as functions
called inside with_libc might throw some exceptions that need to be
handled elsewhere.
For now the best fix seems to wrap only the necessary
Hello Boris,
On Tue, Mar 14, 2017 at 03:11:27PM +0100, Boris Mulder wrote:
> Whenever I throw an exception somewhere in code inside a with_libc
> lambda expression, and try to catch it outside of that block, it will
> not catch that exception.
As I know the inner workings of the libc execution mo
Hi all,
Whenever I throw an exception somewhere in code inside a with_libc
lambda expression, and try to catch it outside of that block, it will
not catch that exception.
Example:
|t||ry {|
|Libc::with_libc([&] () { ... throw E||xception();
... } );|
|} catch (E
