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
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
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
Incorrect processing (truncation) of SQL statement with length 10MB+1
-
Key: CORE-5382
URL: http://tracker.firebirdsql.org/browse/CORE-5382
Project: Firebird Core
Issue
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.
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
On 10/26/16 12:29, marius adrian popa wrote:
Any ideas ?
This happens only on Android build with master (3.0 branch builds ok)
make yvalve
make[4]: Entering directory '/home/mariuz/Work/firebird/firebird/gen'
Any ideas ?
This happens only on Android build with master (3.0 branch builds ok)
make yvalve
make[4]: Entering directory '/home/mariuz/Work/firebird/firebird/gen'
/home/mariuz/android-ndk-r13/toolchains/x86_64-4.9/prebuilt/linux-x86_64/bin/x86_64-linux-android-g++