In general you should only call produce() and consume() from within
general_work(), and, really, you only need to consume() because
produce() can be called with the return value from the function call
(or, return WORK_CALLED_PRODUCE to indicate as much). The other block
types (e.g. sync), call
On Sun, 19 Nov 2017 at 13:16:14 -0500, Michael Dickens wrote:
> You can safely call produce() and consume() multiple times in the same
> work() call: yes!
I assume this also applies to general_work()?
> Note that by doing so, if you're using the nitems_written() or
> nitems_read() [e.g., for
You can safely call produce() and consume() multiple times in the same
work() call: yes!
Note that by doing so, if you're using the nitems_written() or
nitems_read() [e.g., for finding or writing tags], then those values
will be updated when you call produce() and consume() -BUT- inside the
On 19/11/17 17:22, rear1019 wrote:
> I have a question regarding the usage of produce() and consume(): Is it
> safe to call these functions multiple times? Or must the calls be
> merged into a single one?
consume() in the end calls buffer_reader::update_read_pointer(int
nitems) which again calls
Hello,
I have a question regarding the usage of produce() and consume(): Is it
safe to call these functions multiple times? Or must the calls be
merged into a single one?
Documentation of consume() [1] states that “this function should be
called at the end of work() or general_work(), after all