Subject: Re: [boost] review request for boost.context
From: Emil Dotchevski (emil_at_[hidden])
Date: 2010-07-28 14:46:59
On Wed, Jul 28, 2010 at 11:41 AM, Oliver Kowalke <k-oli_at_[hidden]> wrote:
> Am 28.07.2010 20:28, schrieb Emil Dotchevski:
>> On Wed, Jul 28, 2010 at 7:08 AM, Oliver Kowalke<k-oli_at_[hidden]> wrote:
>>>> How does it behave under c++ exceptions?
>>> Exceptions must catched inside the function invoked by boost::context -
>>> not sj/lj exception model is used (DWARF instead) -> see docu.
>> Wouldn't it be nicer if the framework catches exceptions from the
>> functions and then propagates them to the caller from jump_to() or a
>> special function exception_ptr get_error()?
> No, because boost.context behaves like POSIX ucontext. The app exits if the
> function executed by the context ends.
I'm not familiar with ucontext, what is the rationale for that
behavior? How do I go about creating a system where contexts are
created and destroyed dynamically?
Reverge Studios, Inc.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk