$include_dir="/home/hyper-archives/boost/include"; include("$include_dir/msg-header.inc") ?>
Subject: Re: [boost] [context] Implementation comments
From: vicente.botet (vicente.botet_at_[hidden])
Date: 2011-01-20 14:51:57
----- Original Message -----
From: "Oliver Kowalke" <k-oli_at_[hidden]>
To: <boost_at_[hidden]>
Sent: Thursday, January 20, 2011 8:38 PM
Subject: Re: [boost] [context] Implementation comments
> Am 20.01.2011 08:23, schrieb vicente.botet:
>> The library could provide some stack allocation mechanisms which will take care of whether the implementation is using the Windows Fiber API. A user should be able to define its own allocation stack mechanism and be as efficient as possible if s/he takes in account detail implementation information provided by Boost.Context through for example a macro, BOOST_CONTEXT_MANAGE_THE_STACK or somthing like that.
>
> If the ctor of boost::context takes an allocator-like object to allocate
> stack (how the space will be allocated can be specialized by the user) -
> should the lib ignore the allocator if Windows Fibers are used internally?
> What recommends the boost standard?
I like the allocator idea. It seems to me evident that in this case the allocator shouldn't be used as there is no need to allocate the stack.
Vicente