summaryrefslogtreecommitdiffstatshomepage
path: root/3rdparty/asio/src/doc/requirements/read_write_operations.qbk
diff options
context:
space:
mode:
Diffstat (limited to '3rdparty/asio/src/doc/requirements/read_write_operations.qbk')
-rw-r--r--3rdparty/asio/src/doc/requirements/read_write_operations.qbk34
1 files changed, 34 insertions, 0 deletions
diff --git a/3rdparty/asio/src/doc/requirements/read_write_operations.qbk b/3rdparty/asio/src/doc/requirements/read_write_operations.qbk
new file mode 100644
index 00000000000..d7185a9beaf
--- /dev/null
+++ b/3rdparty/asio/src/doc/requirements/read_write_operations.qbk
@@ -0,0 +1,34 @@
+[/
+ / Copyright (c) 2003-2016 Christopher M. Kohlhoff (chris at kohlhoff dot com)
+ /
+ / Distributed under the Boost Software License, Version 1.0. (See accompanying
+ / file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
+ /]
+
+[section:read_write_operations Requirements on read and write operations]
+
+A ['read operation] is an operation that reads data into a mutable buffer
+sequence argument of a type meeting [link asio.reference.MutableBufferSequence
+`MutableBufferSequence`] requirements. The mutable buffer sequence specifies
+memory where the data should be placed. A read operation shall always fill a
+buffer in the sequence completely before proceeding to the next.
+
+A ['write operation] is an operation that writes data from a constant buffer
+sequence argument of a type meeting [link asio.reference.ConstBufferSequence
+`ConstBufferSequence`] requirements. The constant buffer sequence specifies
+memory where the data to be written is located. A write operation shall always
+write a buffer in the sequence completely before proceeding to the next.
+
+If a read or write operation is also an [link
+asio.reference.asynchronous_operations asynchronous operation], the operation
+shall maintain one or more copies of the buffer sequence until such time as the
+operation no longer requires access to the memory specified by the buffers in
+the sequence. The program shall ensure the memory remains valid until:
+
+[mdash] the last copy of the buffer sequence is destroyed, or
+
+[mdash] the completion handler for the asynchronous operation is invoked,
+
+whichever comes first.
+
+[endsect]
ommitgraph'>* layout doc: correction and add inputraw (this one actually does work the way ... hap2019-03-241-6/+9 * device_memory_interface.rst : Correct docs cam9002019-02-181-1/+1 * 2018 -> 2019 changes (nw) Stiletto2019-01-101-2/+2 * Make informational verbs a bit more consistent, reduce copy/pasted code, a sl... Vas Crabb2019-01-041-4/+4 * srcclean and cleanup (nw) Vas Crabb2018-10-281-0/+6 * Fixed broken document structure Wellington Uemura2018-10-041-18/+22 * finish off layout documentation for now Vas Crabb2018-08-031-8/+112 * (nw) Further layout work: Vas Crabb2018-08-021-0/+191 * (nw) be less eager to shadow variables in layouts, make highlights visible on... Vas Crabb2018-07-311-18/+21 * (nw) more layout documentation