Re: [Firebird-devel] Coroutines

2016-10-26 Thread Roman Simakov
With callbacks you will smear code over two methods: caller, callback. Also you will need to keep some state! AFAIU coroutins solve this problem in more elegant manner using saving running context. Operator A push a portion of data to pipe and *goto* operator B which pull the portion process it

Re: [Firebird-devel] Coroutines

2016-10-26 Thread Egor Pugin
Why not callbacks? On 26 October 2016 at 15:51, Roman Simakov wrote: > 2016-10-26 15:24 GMT+03:00 Dimitry Sibiryakov : >> It must be more than just nice to add gigabyte of boost sources or 30 >> megabytes library >> to Firebird > > I guess it's

Re: [Firebird-devel] Coroutines

2016-10-26 Thread Roman Simakov
2016-10-26 15:24 GMT+03:00 Dimitry Sibiryakov : > It must be more than just nice to add gigabyte of boost sources or 30 > megabytes library > to Firebird I guess it's not about boost but about approach. I thought about the same approach in SciDB to provide nice way to

Re: [Firebird-devel] Coroutines

2016-10-26 Thread Dimitry Sibiryakov
26.10.2016 13:33, Adriano dos Santos Fernandes wrote: > This is so nice (and apparent fast in Linux) that I'm going to > investigate further. It must be more than just nice to add gigabyte of boost sources or 30 megabytes library to Firebird. -- WBR, SD.

[Firebird-devel] Coroutines

2016-10-26 Thread Adriano dos Santos Fernandes
Hi! Learning node.js and its single-threaded model with asynchronous execution, I looked for things that can improve Firebird as well. It's obvious that things like boost asio may be a good thing when dealing with sockets and filesystem, but is not subject of this thread. Today I got up