Re: [Boost-users] Forthcoming Boost.Fiber review

Subject: Re: [Boost-users] Forthcoming Boost.Fiber review
From: Carlos Ferreira (carlosmf.pt_at_[hidden])
Date: 2014-01-27 20:59:05

Hello Again

This time, I'm having a weird problem, when setting the scheduler.

If I have this

> boost::asio::io_service &ioService(std::get<0>(*ioService_sPtr));
> boost::fibers::asio::round_robin ds(ioService);
> boost::fibers::set_scheduling_algorithm(&ds);
> boost::asio::io_service::work workLine(ioService);
> ioService.run();

where  ioService_sPtr is a pointer to a ioService already instantiated, the
ioService.run() will return when the first yield returns the coroutine,
ending the thread execution. If I don't set a scheduling algorithm, the
run() will work properly, waiting for a job to execute or until stop() is
called.

Is this a normal behaviour?
Thank you!

On 27 January 2014 16:02, Carlos Ferreira <carlosmf.pt_at_[hidden]> wrote:

> Never mind...
> I was including the spawn.hpp from asio which was breaking everything...
> Still, I don't know why it was compiling without problems, with the
> Arch-linux boost...
>
>
> On 27 January 2014 15:52, Carlos Ferreira <carlosmf.pt_at_[hidden]> wrote:
>
>> Ok, this may also help.
>>
>> include/boost/asio/spawn.hpp:90:7: error: ‘caller_type’ has not been
>>> declared
>>> include/boost/asio/spawn.hpp:128:3: error: ‘caller_type’ does not name a
>>> type
>>> include/boost/asio/spawn.hpp:92:7: error: class
>>> ‘boost::asio::basic_yield_context<Handler>’ does not have any field named
>>> ‘ca_’
>>
>>
>>
>>
>>
>> On 27 January 2014 13:43, Carlos Ferreira <carlosmf.pt_at_[hidden]> wrote:
>>
>>> Well this is a bit strange because the arch linux boost version is the
>>> 1.55 and the git clone that I got from the git boost repo, is also the 1.55
>>>
>>> Why is one version working and the other isn't ?
>>>
>>>
>>> On 27 January 2014 13:34, Oliver Kowalke <oliver.kowalke_at_[hidden]>wrote:
>>>
>>>> 2014-01-27 Carlos Ferreira <carlosmf.pt_at_[hidden]>
>>>>
>>>>
>>>>> boost/boost/asio/impl/spawn.hpp:263:77: error: no matching function
>>>>>> for call to
>>>>>> ‘boost::coroutines::coroutine<void()>::coroutine(boost::coroutines::attributes&)’
>>>>>>
>>>>>
>>>> this comes from boost.asio and 'coroutine<void()>' is the old coroutine
>>>> interface (deprecated)
>>>>
>>>> _______________________________________________
>>>> Boost-users mailing list
>>>> Boost-users_at_[hidden]
>>>> http://lists.boost.org/mailman/listinfo.cgi/boost-users
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> Carlos Miguel Ferreira
>>> Researcher at Telecommunications Institute
>>> Aveiro - Portugal
>>> Work E-mail - cmf_at_[hidden]
>>> Skype & GTalk -> carlosmf.pt_at_[hidden]
>>> LinkedIn -> http://www.linkedin.com/in/carlosmferreira
>>>
>>
>>
>>
>> --
>>
>> Carlos Miguel Ferreira
>> Researcher at Telecommunications Institute
>> Aveiro - Portugal
>> Work E-mail - cmf_at_[hidden]
>> Skype & GTalk -> carlosmf.pt_at_[hidden]
>> LinkedIn -> http://www.linkedin.com/in/carlosmferreira
>>
>
>
>
> --
>
> Carlos Miguel Ferreira
> Researcher at Telecommunications Institute
> Aveiro - Portugal
> Work E-mail - cmf_at_[hidden]
> Skype & GTalk -> carlosmf.pt_at_[hidden]
> LinkedIn -> http://www.linkedin.com/in/carlosmferreira
>

-- 
Carlos Miguel Ferreira
Researcher at Telecommunications Institute
Aveiro - Portugal
Work E-mail - cmf_at_[hidden]
Skype & GTalk -> carlosmf.pt_at_[hidden]
LinkedIn -> http://www.linkedin.com/in/carlosmferreira