Re: [Kicad-developers] Coroutines, in general

2017-02-23 Thread Joakim Asplund
Hi, For what it's worth, I've been bitten by some changes in boost coroutine(s?)(2) and there are actually two different interfaces (coroutines and coroutines2) and the previous is deprecated. My workaround is to do the following in our project to get something that works both before boost 1.55 a

Re: [Kicad-developers] Coroutines, in general

2017-02-23 Thread Chris Pavlina
Fair enough. Has coroutine really been as bad as context though? Seems we've had to resort to using some internal API functions in context, which really seems to be screwing us over.. :P On Thu, Feb 23, 2017 at 02:27:59PM +0100, Tomasz Wlostowski wrote: > On 23.02.2017 14:17, Chris Pavlina wrote:

Re: [Kicad-developers] Coroutines, in general

2017-02-23 Thread Tomasz Wlostowski
On 23.02.2017 14:17, Chris Pavlina wrote: > boost::coroutine? Seems the latter has a much more stable API, is > it missing something we require? Hi Chris, I can't agree that either boost::context or boost::coroutine have stable APIs, that's why have our own wrapper on top... Cheers, Tom ___

[Kicad-developers] Coroutines, in general

2017-02-23 Thread Chris Pavlina
Hi, Just out of curiosity, I'm not sure what the reasoning is here and nobody on IRC really knew last night --- can anyone explain why we use boost::context with our own coroutine implementation on top, rather than using boost::coroutine? Seems the latter has a much more stable API, is it missin