Update of /cvsroot/boost/boost/libs/asio/doc/requirements
In directory sc8-pr-cvs3.sourceforge.net:/tmp/cvs-serv24810/requirements
Modified Files:
AcceptHandler.qbk AsyncReadStream.qbk AsyncWriteStream.qbk
CompletionHandler.qbk ConnectHandler.qbk
ConstBufferSequence.qbk DatagramSocketService.qbk Endpoint.qbk
GettableSocketOption.qbk InternetProtocol.qbk
IoObjectService.qbk MutableBufferSequence.qbk Protocol.qbk
ReadHandler.qbk ResolveHandler.qbk ResolverService.qbk
SettableSocketOption.qbk SocketAcceptorService.qbk
SocketService.qbk StreamSocketService.qbk SyncReadStream.qbk
SyncWriteStream.qbk TimerService.qbk WaitHandler.qbk
WriteHandler.qbk asynchronous_operations.qbk
Log Message:
Documentation updates.
Index: AcceptHandler.qbk
===================================================================
RCS file: /cvsroot/boost/boost/libs/asio/doc/requirements/AcceptHandler.qbk,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- AcceptHandler.qbk 6 Jan 2007 10:59:59 -0000 1.2
+++ AcceptHandler.qbk 16 May 2007 14:35:09 -0000 1.3
@@ -8,7 +8,7 @@
[section:AcceptHandler Accept handler requirements]
An accept handler must meet the requirements for a [link
-boost_asio.requirements.Handler handler]. A value `h` of an accept handler
+boost_asio.reference.Handler handler]. A value `h` of an accept handler
class should work correctly in the expression `h(ec)`, where `ec` is an lvalue
of type `const error_code`.
Index: AsyncReadStream.qbk
===================================================================
RCS file: /cvsroot/boost/boost/libs/asio/doc/requirements/AsyncReadStream.qbk,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- AsyncReadStream.qbk 6 Jan 2007 10:59:59 -0000 1.2
+++ AsyncReadStream.qbk 16 May 2007 14:35:09 -0000 1.3
@@ -9,9 +9,9 @@
In the table below, `a` denotes an asynchronous read stream object, `mb`
denotes an object satisfying [link
-boost_asio.requirements.MutableBufferSequence mutable buffer sequence]
+boost_asio.reference.MutableBufferSequence mutable buffer sequence]
requirements, and `h` denotes an object satisfying [link
-boost_asio.requirements.ReadHandler read handler] requirements.
+boost_asio.reference.ReadHandler read handler] requirements.
[table Buffer-oriented asynchronous read stream requirements
[[operation] [type] [semantics, pre/post-conditions]]
@@ -28,7 +28,7 @@
Initiates an asynchronous operation to read one or more bytes of data
from the stream `a`. The operation is performed via the `io_service`
object `a.io_service()` and behaves according to [link
- boost_asio.requirements.asynchronous_operations asynchronous operation]
+ boost_asio.reference.asynchronous_operations asynchronous operation]
requirements.\n
\n
The mutable buffer sequence `mb` specifies memory where the data should
Index: AsyncWriteStream.qbk
===================================================================
RCS file: /cvsroot/boost/boost/libs/asio/doc/requirements/AsyncWriteStream.qbk,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- AsyncWriteStream.qbk 6 Jan 2007 10:59:59 -0000 1.2
+++ AsyncWriteStream.qbk 16 May 2007 14:35:09 -0000 1.3
@@ -8,9 +8,9 @@
[section:AsyncWriteStream Buffer-oriented asynchronous write stream
requirements]
In the table below, `a` denotes an asynchronous write stream object, `cb`
-denotes an object satisfying [link boost_asio.requirements.ConstBufferSequence
+denotes an object satisfying [link boost_asio.reference.ConstBufferSequence
constant buffer sequence] requirements, and `h` denotes an object satisfying
-[link boost_asio.requirements.WriteHandler write handler] requirements.
+[link boost_asio.reference.WriteHandler write handler] requirements.
[table Buffer-oriented asynchronous write stream requirements
[[operation] [type] [semantics, pre/post-conditions]]
@@ -27,7 +27,7 @@
Initiates an asynchronous operation to write one or more bytes of data to
the stream `a`. The operation is performed via the `io_service` object
`a.io_service()` and behaves according to [link
- boost_asio.requirements.asynchronous_operations asynchronous operation]
+ boost_asio.reference.asynchronous_operations asynchronous operation]
requirements.\n
\n
The constant buffer sequence `cb` specifies memory where the data to be
Index: CompletionHandler.qbk
===================================================================
RCS file:
/cvsroot/boost/boost/libs/asio/doc/requirements/CompletionHandler.qbk,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- CompletionHandler.qbk 6 Jan 2007 10:59:59 -0000 1.2
+++ CompletionHandler.qbk 16 May 2007 14:35:09 -0000 1.3
@@ -8,7 +8,7 @@
[section:CompletionHandler Completion handler requirements]
A completion handler must meet the requirements for a [link
-boost_asio.requirements.Handler handler]. A value `h` of a completion handler
+boost_asio.reference.Handler handler]. A value `h` of a completion handler
class should work correctly in the expression `h()`.
[endsect]
Index: ConnectHandler.qbk
===================================================================
RCS file: /cvsroot/boost/boost/libs/asio/doc/requirements/ConnectHandler.qbk,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- ConnectHandler.qbk 6 Jan 2007 10:59:59 -0000 1.2
+++ ConnectHandler.qbk 16 May 2007 14:35:09 -0000 1.3
@@ -8,7 +8,7 @@
[section:ConnectHandler Connect handler requirements]
A connect handler must meet the requirements for a [link
-boost_asio.requirements.Handler handler]. A value `h` of a connect handler
+boost_asio.reference.Handler handler]. A value `h` of a connect handler
class should work correctly in the expression `h(ec)`, where `ec` is an lvalue
of type `const error_code`.
Index: ConstBufferSequence.qbk
===================================================================
RCS file:
/cvsroot/boost/boost/libs/asio/doc/requirements/ConstBufferSequence.qbk,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- ConstBufferSequence.qbk 6 Jan 2007 11:00:00 -0000 1.2
+++ ConstBufferSequence.qbk 16 May 2007 14:35:09 -0000 1.3
@@ -16,7 +16,7 @@
[`X::value_type`]
[`T`]
[`T` meets the requirements for [link
- boost_asio.requirements.ConvertibleToConstBuffer
+ boost_asio.reference.ConvertibleToConstBuffer
ConvertibleToConstBuffer].]
]
[
Index: DatagramSocketService.qbk
===================================================================
RCS file:
/cvsroot/boost/boost/libs/asio/doc/requirements/DatagramSocketService.qbk,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- DatagramSocketService.qbk 6 Jan 2007 11:00:00 -0000 1.2
+++ DatagramSocketService.qbk 16 May 2007 14:35:09 -0000 1.3
@@ -8,20 +8,20 @@
[section:DatagramSocketService Datagram socket service requirements]
A datagram socket service must meet the requirements for a [link
-boost_asio.requirements.SocketService socket service], as well as the
+boost_asio.reference.SocketService socket service], as well as the
additional requirements listed below.
In the table below, `X` denotes a datagram socket service class for protocol
-[link boost_asio.requirements.Protocol `Protocol`], `a` denotes a value of type
+[link boost_asio.reference.Protocol `Protocol`], `a` denotes a value of type
`X`, `b` denotes a value of type `X::implementation_type`, `e` denotes a value
of type `Protocol::endpoint`, `ec` denotes a value of type `error_code`, `f`
denotes a value of type `socket_base::message_flags`, `mb` denotes a value
-satisfying [link boost_asio.requirements.MutableBufferSequence mutable buffer
+satisfying [link boost_asio.reference.MutableBufferSequence mutable buffer
sequence] requirements, `rh` denotes a value meeting [link
-boost_asio.requirements.ReadHandler `ReadHandler`] requirements, `cb` denotes a
-value satisfying [link boost_asio.requirements.ConstBufferSequence constant
+boost_asio.reference.ReadHandler `ReadHandler`] requirements, `cb` denotes a
+value satisfying [link boost_asio.reference.ConstBufferSequence constant
buffer sequence] requirements, and `wh` denotes a value meeting [link
-boost_asio.requirements.WriteHandler `WriteHandler`] requirements.
+boost_asio.reference.WriteHandler `WriteHandler`] requirements.
[table DatagramSocketService requirements
[[expression] [return type] [assertion/note\npre/post-condition]]
@@ -49,7 +49,7 @@
Initiates an asynchronous operation to read one or more bytes of data
from a connected socket `b`. The operation is performed via the
`io_service` object `a.io_service()` and behaves according to [link
- boost_asio.requirements.asynchronous_operations asynchronous operation]
+ boost_asio.reference.asynchronous_operations asynchronous operation]
requirements.\n
\n
The mutable buffer sequence `mb` specifies memory where the data should
@@ -96,7 +96,7 @@
Initiates an asynchronous operation to read one or more bytes of data
from an unconnected socket `b`. The operation is performed via the
`io_service` object `a.io_service()` and behaves according to [link
- boost_asio.requirements.asynchronous_operations asynchronous operation]
+ boost_asio.reference.asynchronous_operations asynchronous operation]
requirements.\n
\n
The mutable buffer sequence `mb` specifies memory where the data should
@@ -146,7 +146,7 @@
Initiates an asynchronous operation to write one or more bytes of data to
a connected socket `b`. The operation is performed via the `io_service`
object `a.io_service()` and behaves according to [link
- boost_asio.requirements.asynchronous_operations asynchronous operation]
+ boost_asio.reference.asynchronous_operations asynchronous operation]
requirements.\n
\n
The constant buffer sequence `cb` specifies memory where the data to be
@@ -199,7 +199,7 @@
Initiates an asynchronous operation to write one or more bytes of data to
an unconnected socket `b`. The operation is performed via the
`io_service`
object `a.io_service()` and behaves according to [link
- boost_asio.requirements.asynchronous_operations asynchronous operation]
+ boost_asio.reference.asynchronous_operations asynchronous operation]
requirements.\n
\n
The constant buffer sequence `cb` specifies memory where the data to be
Index: Endpoint.qbk
===================================================================
RCS file: /cvsroot/boost/boost/libs/asio/doc/requirements/Endpoint.qbk,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- Endpoint.qbk 6 Jan 2007 11:00:00 -0000 1.2
+++ Endpoint.qbk 16 May 2007 14:35:09 -0000 1.3
@@ -17,7 +17,7 @@
[[expression] [type] [assertion/note\npre/post-conditions]]
[
[`X::protocol_type`]
- [type meeting [link boost_asio.requirements.Protocol protocol]
requirements]
+ [type meeting [link boost_asio.reference.Protocol protocol] requirements]
[]
]
[
Index: GettableSocketOption.qbk
===================================================================
RCS file:
/cvsroot/boost/boost/libs/asio/doc/requirements/GettableSocketOption.qbk,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- GettableSocketOption.qbk 6 Jan 2007 11:00:00 -0000 1.2
+++ GettableSocketOption.qbk 16 May 2007 14:35:09 -0000 1.3
@@ -8,7 +8,7 @@
[section:GettableSocketOption Gettable socket option requirements]
In the table below, `X` denotes a socket option class, `a` denotes a value of
-`X`, `p` denotes a value that meets the [link boost_asio.requirements.Protocol
+`X`, `p` denotes a value that meets the [link boost_asio.reference.Protocol
protocol] requirements, and `u` denotes an identifier.
[table GettableSocketOption requirements
Index: InternetProtocol.qbk
===================================================================
RCS file: /cvsroot/boost/boost/libs/asio/doc/requirements/InternetProtocol.qbk,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- InternetProtocol.qbk 6 Jan 2007 11:00:00 -0000 1.2
+++ InternetProtocol.qbk 16 May 2007 14:35:09 -0000 1.3
@@ -8,7 +8,7 @@
[section:InternetProtocol Internet protocol requirements]
An internet protocol must meet the requirements for a [link
-boost_asio.requirements.Protocol protocol] as well as the additional
+boost_asio.reference.Protocol protocol] as well as the additional
requirements listed below.
In the table below, `X` denotes an internet protocol class, `a` denotes a value
Index: IoObjectService.qbk
===================================================================
RCS file: /cvsroot/boost/boost/libs/asio/doc/requirements/IoObjectService.qbk,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- IoObjectService.qbk 6 Jan 2007 11:00:00 -0000 1.2
+++ IoObjectService.qbk 16 May 2007 14:35:09 -0000 1.3
@@ -8,7 +8,7 @@
[section:IoObjectService I/O object service requirements]
An I/O object service must meet the requirements for a [link
-boost_asio.requirements.Service service], as well as the requirements listed
+boost_asio.reference.Service service], as well as the requirements listed
below.
In the table below, `X` denotes an I/O object service class, `a` denotes a
Index: MutableBufferSequence.qbk
===================================================================
RCS file:
/cvsroot/boost/boost/libs/asio/doc/requirements/MutableBufferSequence.qbk,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- MutableBufferSequence.qbk 6 Jan 2007 11:00:00 -0000 1.2
+++ MutableBufferSequence.qbk 16 May 2007 14:35:09 -0000 1.3
@@ -16,7 +16,7 @@
[`X::value_type`]
[`T`]
[`T` meets the requirements for [link
- boost_asio.requirements.ConvertibleToMutableBuffer
+ boost_asio.reference.ConvertibleToMutableBuffer
ConvertibleToMutableBuffer].]
]
[
Index: Protocol.qbk
===================================================================
RCS file: /cvsroot/boost/boost/libs/asio/doc/requirements/Protocol.qbk,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- Protocol.qbk 6 Jan 2007 11:00:00 -0000 1.2
+++ Protocol.qbk 16 May 2007 14:35:09 -0000 1.3
@@ -17,7 +17,7 @@
[[expression] [return type] [assertion/note\npre/post-conditions]]
[
[`X::endpoint`]
- [type meeting [link boost_asio.requirements.Endpoint endpoint]
requirements]
+ [type meeting [link boost_asio.reference.Endpoint endpoint] requirements]
[]
]
[
Index: ReadHandler.qbk
===================================================================
RCS file: /cvsroot/boost/boost/libs/asio/doc/requirements/ReadHandler.qbk,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- ReadHandler.qbk 6 Jan 2007 11:00:00 -0000 1.2
+++ ReadHandler.qbk 16 May 2007 14:35:09 -0000 1.3
@@ -8,7 +8,7 @@
[section:ReadHandler Read handler requirements]
A read handler must meet the requirements for a [link
-boost_asio.requirements.Handler handler]. A value `h` of a read handler class
+boost_asio.reference.Handler handler]. A value `h` of a read handler class
should work correctly in the expression `h(ec, s)`, where `ec` is an lvalue of
type `const error_code` and `s` is an lvalue of type `const size_t`.
Index: ResolveHandler.qbk
===================================================================
RCS file: /cvsroot/boost/boost/libs/asio/doc/requirements/ResolveHandler.qbk,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- ResolveHandler.qbk 6 Apr 2007 08:17:07 -0000 1.3
+++ ResolveHandler.qbk 16 May 2007 14:35:09 -0000 1.4
@@ -8,7 +8,7 @@
[section:ResolveHandler Resolve handler requirements]
A resolve handler must meet the requirements for a [link
-boost_asio.requirements.Handler handler]. A value `h` of a resolve handler
+boost_asio.reference.Handler handler]. A value `h` of a resolve handler
class should work correctly in the expression `h(ec, i)`, where `ec` is an
lvalue of type `const error_code` and `i` is an lvalue of type `const
ip::basic_resolver_iterator<InternetProtocol>`. `InternetProtocol` is the
Index: ResolverService.qbk
===================================================================
RCS file: /cvsroot/boost/boost/libs/asio/doc/requirements/ResolverService.qbk,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- ResolverService.qbk 6 Jan 2007 11:00:00 -0000 1.2
+++ ResolverService.qbk 16 May 2007 14:35:09 -0000 1.3
@@ -8,7 +8,7 @@
[section:ResolverService Resolver service requirements]
A resolver service must meet the requirements for an [link
-boost_asio.requirements.IoObjectService I/O object service], as well as the
+boost_asio.reference.IoObjectService I/O object service], as well as the
additional requirements listed below.
In the table below, `X` denotes a resolver service class for protocol
@@ -17,7 +17,7 @@
`ip::basic_resolver_query<InternetProtocol>`, `e` denotes a value of type
`ip::basic_endpoint<InternetProtocol>`, `ec` denotes a value of type
`error_code`, and `h` denotes a value meeting [link
-boost_asio.requirements.ResolveHandler `ResolveHandler`] requirements.
+boost_asio.reference.ResolveHandler `ResolveHandler`] requirements.
[table ResolverService requirements
[[expression] [return type] [assertion/note\npre/post-condition]]
@@ -25,7 +25,7 @@
[`a.destroy(b);`]
[]
[
- From [link boost_asio.requirements.IoObjectService IoObjectService]
+ From [link boost_asio.reference.IoObjectService IoObjectService]
requirements. Implicitly cancels asynchronous resolve operations, as if
by
calling `a.cancel(b, ec)`.
]
@@ -63,7 +63,7 @@
[
Initiates an asynchronous resolve operation that is performed via the
`io_service` object `a.io_service()` and behaves according to [link
- boost_asio.requirements.asynchronous_operations asynchronous operation]
+ boost_asio.reference.asynchronous_operations asynchronous operation]
requirements.\n
\n
If the operation completes successfully, the `ResolveHandler` object `h`
@@ -94,7 +94,7 @@
[
Initiates an asynchronous resolve operation that is performed via the
`io_service` object `a.io_service()` and behaves according to [link
- boost_asio.requirements.asynchronous_operations asynchronous operation]
+ boost_asio.reference.asynchronous_operations asynchronous operation]
requirements.\n
\n
If the operation completes successfully, the `ResolveHandler` object `h`
Index: SettableSocketOption.qbk
===================================================================
RCS file:
/cvsroot/boost/boost/libs/asio/doc/requirements/SettableSocketOption.qbk,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- SettableSocketOption.qbk 6 Jan 2007 11:00:00 -0000 1.2
+++ SettableSocketOption.qbk 16 May 2007 14:35:09 -0000 1.3
@@ -8,7 +8,7 @@
[section:SettableSocketOption Settable socket option requirements]
In the table below, `X` denotes a socket option class, `a` denotes a value of
-`X`, `p` denotes a value that meets the [link boost_asio.requirements.Protocol
+`X`, `p` denotes a value that meets the [link boost_asio.reference.Protocol
protocol] requirements, and `u` denotes an identifier.
[table SettableSocketOption requirements
Index: SocketAcceptorService.qbk
===================================================================
RCS file:
/cvsroot/boost/boost/libs/asio/doc/requirements/SocketAcceptorService.qbk,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- SocketAcceptorService.qbk 6 Jan 2007 11:00:00 -0000 1.2
+++ SocketAcceptorService.qbk 16 May 2007 14:35:09 -0000 1.3
@@ -8,23 +8,23 @@
[section:SocketAcceptorService Socket acceptor service requirements]
A socket acceptor service must meet the requirements for an [link
-boost_asio.requirements.IoObjectService I/O object service], as well as the
+boost_asio.reference.IoObjectService I/O object service], as well as the
additional requirements listed below.
In the table below, `X` denotes a socket acceptor service class for protocol
-[link boost_asio.requirements.Protocol `Protocol`], `a` denotes a value of type
+[link boost_asio.reference.Protocol `Protocol`], `a` denotes a value of type
`X`, `b` denotes a value of type `X::implementation_type`, `p` denotes a value
of type `Protocol`, `n` denotes a value of type `X::native_type`, `e` denotes a
value of type `Protocol::endpoint`, `ec` denotes a value of type `error_code`,
-`s` denotes a value meeting [link boost_asio.requirements.SettableSocketOption
+`s` denotes a value meeting [link boost_asio.reference.SettableSocketOption
`SettableSocketOption`] requirements, `g` denotes a value meeting [link
-boost_asio.requirements.GettableSocketOption `GettableSocketOption`]
+boost_asio.reference.GettableSocketOption `GettableSocketOption`]
requirements, `i` denotes a value meeting [link
-boost_asio.requirements.IoControlCommand `IoControlCommand`] requirements, `k`
+boost_asio.reference.IoControlCommand `IoControlCommand`] requirements, `k`
denotes a value of type `basic_socket<Protocol, SocketService>` where
-`SocketService` is a type meeting [link boost_asio.requirements.SocketService
+`SocketService` is a type meeting [link boost_asio.reference.SocketService
socket service] requirements, `ah` denotes a value meeting [link
-boost_asio.requirements.AcceptHandler `AcceptHandler`] requirements, and `u`
+boost_asio.reference.AcceptHandler `AcceptHandler`] requirements, and `u`
and `v` denote identifiers.
[table SocketAcceptorService requirements
@@ -42,7 +42,7 @@
[`a.construct(b);`]
[]
[
- From [link boost_asio.requirements.IoObjectService IoObjectService]
+ From [link boost_asio.reference.IoObjectService IoObjectService]
requirements.\n
post: `!a.is_open(b)`.
]
@@ -51,7 +51,7 @@
[`a.destroy(b);`]
[]
[
- From [link boost_asio.requirements.IoObjectService IoObjectService]
+ From [link boost_asio.reference.IoObjectService IoObjectService]
requirements. Implicitly cancels asynchronous operations, as if by
calling
`a.close(b, ec)`.
]
@@ -223,7 +223,7 @@
pre: `a.is_open(b) && !k.is_open()`.\n
Initiates an asynchronous accept operation that is performed via the
`io_service` object `a.io_service()` and behaves according to [link
- boost_asio.requirements.asynchronous_operations asynchronous operation]
+ boost_asio.reference.asynchronous_operations asynchronous operation]
requirements.\n\n
The program must ensure the objects `k` and `e` are valid until the
handler for the asynchronous operation is invoked.
@@ -238,7 +238,7 @@
pre: `a.is_open(b) && !k.is_open()`.\n
Initiates an asynchronous accept operation that is performed via the
`io_service` object `a.io_service()` and behaves according to [link
- boost_asio.requirements.asynchronous_operations asynchronous operation]
+ boost_asio.reference.asynchronous_operations asynchronous operation]
requirements.\n\n
The program must ensure the object `k` is valid until the handler for the
asynchronous operation is invoked.
Index: SocketService.qbk
===================================================================
RCS file: /cvsroot/boost/boost/libs/asio/doc/requirements/SocketService.qbk,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- SocketService.qbk 6 Jan 2007 11:00:00 -0000 1.2
+++ SocketService.qbk 16 May 2007 14:35:09 -0000 1.3
@@ -8,21 +8,21 @@
[section:SocketService Socket service requirements]
A socket service must meet the requirements for an [link
-boost_asio.requirements.IoObjectService I/O object service], as well as the
+boost_asio.reference.IoObjectService I/O object service], as well as the
additional requirements listed below.
In the table below, `X` denotes a socket service class for protocol [link
-boost_asio.requirements.Protocol `Protocol`], `a` denotes a value of type `X`,
+boost_asio.reference.Protocol `Protocol`], `a` denotes a value of type `X`,
`b` denotes a value of type `X::implementation_type`, `p` denotes a value of
type `Protocol`, `n` denotes a value of type `X::native_type`, `e` denotes a
value of type `Protocol::endpoint`, `ec` denotes a value of type `error_code`,
-`s` denotes a value meeting [link boost_asio.requirements.SettableSocketOption
+`s` denotes a value meeting [link boost_asio.reference.SettableSocketOption
`SettableSocketOption`] requirements, `g` denotes a value meeting [link
-boost_asio.requirements.GettableSocketOption `GettableSocketOption`]
+boost_asio.reference.GettableSocketOption `GettableSocketOption`]
requirements, `i` denotes a value meeting [link
-boost_asio.requirements.IoControlCommand `IoControlCommand`] requirements, `h`
+boost_asio.reference.IoControlCommand `IoControlCommand`] requirements, `h`
denotes a value of type `socket_base::shutdown_type`, `ch` denotes a value
-meeting [link boost_asio.requirements.ConnectHandler `ConnectHandler`]
+meeting [link boost_asio.reference.ConnectHandler `ConnectHandler`]
requirements, and `u` and `v` denote identifiers.
[table SocketService requirements
@@ -40,7 +40,7 @@
[`a.construct(b);`]
[]
[
- From [link boost_asio.requirements.IoObjectService IoObjectService]
+ From [link boost_asio.reference.IoObjectService IoObjectService]
requirements.\n
post: `!a.is_open(b)`.
]
@@ -49,7 +49,7 @@
[`a.destroy(b);`]
[]
[
- From [link boost_asio.requirements.IoObjectService IoObjectService]
+ From [link boost_asio.reference.IoObjectService IoObjectService]
requirements. Implicitly cancels asynchronous operations, as if by
calling
`a.close(b, ec)`.
]
@@ -281,7 +281,7 @@
pre: `a.is_open(b)`.\n
Initiates an asynchronous connect operation that is performed via the
`io_service` object `a.io_service()` and behaves according to [link
- boost_asio.requirements.asynchronous_operations asynchronous operation]
+ boost_asio.reference.asynchronous_operations asynchronous operation]
requirements.
]
]
Index: StreamSocketService.qbk
===================================================================
RCS file:
/cvsroot/boost/boost/libs/asio/doc/requirements/StreamSocketService.qbk,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- StreamSocketService.qbk 6 Jan 2007 11:00:00 -0000 1.2
+++ StreamSocketService.qbk 16 May 2007 14:35:09 -0000 1.3
@@ -8,19 +8,19 @@
[section:StreamSocketService Stream socket service requirements]
A stream socket service must meet the requirements for a [link
-boost_asio.requirements.SocketService socket service], as well as the
additional
+boost_asio.reference.SocketService socket service], as well as the additional
requirements listed below.
In the table below, `X` denotes a stream socket service class, `a` denotes a
value of type `X`, `b` denotes a value of type `X::implementation_type`, `ec`
denotes a value of type `error_code`, `f` denotes a value of type
`socket_base::message_flags`, `mb` denotes a value satisfying [link
-boost_asio.requirements.MutableBufferSequence mutable buffer sequence]
+boost_asio.reference.MutableBufferSequence mutable buffer sequence]
requirements, `rh` denotes a value meeting [link
-boost_asio.requirements.ReadHandler `ReadHandler`] requirements, `cb` denotes a
-value satisfying [link boost_asio.requirements.ConstBufferSequence constant
+boost_asio.reference.ReadHandler `ReadHandler`] requirements, `cb` denotes a
+value satisfying [link boost_asio.reference.ConstBufferSequence constant
buffer sequence] requirements, and `wh` denotes a value meeting [link
-boost_asio.requirements.WriteHandler `WriteHandler`] requirements.
+boost_asio.reference.WriteHandler `WriteHandler`] requirements.
[table StreamSocketService requirements
[[expression] [return type] [assertion/note\npre/post-condition]]
@@ -53,7 +53,7 @@
Initiates an asynchronous operation to read one or more bytes of data
from a connected socket `b`. The operation is performed via the
`io_service` object `a.io_service()` and behaves according to [link
- boost_asio.requirements.asynchronous_operations asynchronous operation]
+ boost_asio.reference.asynchronous_operations asynchronous operation]
requirements.\n
\n
The mutable buffer sequence `mb` specifies memory where the data should
@@ -108,7 +108,7 @@
Initiates an asynchronous operation to write one or more bytes of data to
a connected socket `b`. The operation is performed via the `io_service`
object `a.io_service()` and behaves according to [link
- boost_asio.requirements.asynchronous_operations asynchronous operation]
+ boost_asio.reference.asynchronous_operations asynchronous operation]
requirements.\n
\n
The constant buffer sequence `cb` specifies memory where the data to be
Index: SyncReadStream.qbk
===================================================================
RCS file: /cvsroot/boost/boost/libs/asio/doc/requirements/SyncReadStream.qbk,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- SyncReadStream.qbk 6 Jan 2007 11:00:00 -0000 1.2
+++ SyncReadStream.qbk 16 May 2007 14:35:09 -0000 1.3
@@ -8,7 +8,7 @@
[section:SyncReadStream Buffer-oriented synchronous read stream requirements]
In the table below, `a` denotes a synchronous read stream object, `mb` denotes
-an object satisfying [link boost_asio.requirements.MutableBufferSequence
+an object satisfying [link boost_asio.reference.MutableBufferSequence
mutable buffer sequence] requirements, and `ec` denotes an object of type
`error_code`.
Index: SyncWriteStream.qbk
===================================================================
RCS file: /cvsroot/boost/boost/libs/asio/doc/requirements/SyncWriteStream.qbk,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- SyncWriteStream.qbk 6 Jan 2007 11:00:00 -0000 1.2
+++ SyncWriteStream.qbk 16 May 2007 14:35:09 -0000 1.3
@@ -8,7 +8,7 @@
[section:SyncWriteStream Buffer-oriented synchronous write stream requirements]
In the table below, `a` denotes a synchronous write stream object, `cb` denotes
-an object satisfying [link boost_asio.requirements.ConstBufferSequence constant
+an object satisfying [link boost_asio.reference.ConstBufferSequence constant
buffer sequence] requirements, and `ec` denotes an object of type `error_code`.
[table Buffer-oriented synchronous write stream requirements
Index: TimerService.qbk
===================================================================
RCS file: /cvsroot/boost/boost/libs/asio/doc/requirements/TimerService.qbk,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- TimerService.qbk 6 Jan 2007 11:00:00 -0000 1.2
+++ TimerService.qbk 16 May 2007 14:35:09 -0000 1.3
@@ -8,7 +8,7 @@
[section:TimerService Timer service requirements]
A timer service must meet the requirements for an [link
-boost_asio.requirements.IoObjectService I/O object service], as well as the
+boost_asio.reference.IoObjectService I/O object service], as well as the
additional requirements listed below.
In the table below, `X` denotes a timer service class for time type `Time` and
@@ -16,7 +16,7 @@
of type `X::implementation_type`, `t` denotes a value of type `Time`, `d`
denotes a value of type `TimeTraits::duration_type`, `e` denotes a value of
type `error_code`, and `h` denotes a value meeting [link
-boost_asio.requirements.WaitHandler `WaitHandler`] requirements.
+boost_asio.reference.WaitHandler `WaitHandler`] requirements.
[table TimerService requirements
[[expression] [return type] [assertion/note\npre/post-condition]]
@@ -24,7 +24,7 @@
[`a.destroy(b);`]
[]
[
- From [link boost_asio.requirements.IoObjectService IoObjectService]
+ From [link boost_asio.reference.IoObjectService IoObjectService]
requirements. Implicitly cancels asynchronous wait operations, as if by
calling `a.cancel(b, e)`.
]
@@ -92,7 +92,7 @@
[
Initiates an asynchronous wait operation that is performed via the
`io_service` object `a.io_service()` and behaves according to [link
- boost_asio.requirements.asynchronous_operations asynchronous operation]
+ boost_asio.reference.asynchronous_operations asynchronous operation]
requirements.\n
\n
The handler shall be posted for execution only if the condition
Index: WaitHandler.qbk
===================================================================
RCS file: /cvsroot/boost/boost/libs/asio/doc/requirements/WaitHandler.qbk,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- WaitHandler.qbk 6 Jan 2007 11:00:00 -0000 1.2
+++ WaitHandler.qbk 16 May 2007 14:35:09 -0000 1.3
@@ -8,7 +8,7 @@
[section:WaitHandler Wait handler requirements]
A wait handler must meet the requirements for a [link
-boost_asio.requirements.Handler handler]. A value `h` of a wait handler class
+boost_asio.reference.Handler handler]. A value `h` of a wait handler class
should work correctly in the expression `h(ec)`, where `ec` is an lvalue of
type `const error_code`.
Index: WriteHandler.qbk
===================================================================
RCS file: /cvsroot/boost/boost/libs/asio/doc/requirements/WriteHandler.qbk,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- WriteHandler.qbk 6 Jan 2007 11:00:00 -0000 1.2
+++ WriteHandler.qbk 16 May 2007 14:35:09 -0000 1.3
@@ -8,7 +8,7 @@
[section:WriteHandler Write handler requirements]
A write handler must meet the requirements for a [link
-boost_asio.requirements.Handler handler]. A value `h` of a write handler class
+boost_asio.reference.Handler handler]. A value `h` of a write handler class
should work correctly in the expression `h(ec, s)`, where `ec` is an lvalue of
type `const error_code` and `s` is an lvalue of type `const size_t`.
Index: asynchronous_operations.qbk
===================================================================
RCS file:
/cvsroot/boost/boost/libs/asio/doc/requirements/asynchronous_operations.qbk,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- asynchronous_operations.qbk 6 Jan 2007 11:00:01 -0000 1.2
+++ asynchronous_operations.qbk 16 May 2007 14:35:09 -0000 1.3
@@ -12,7 +12,7 @@
['initiating functions].
All initiating functions in Boost.Asio take a function object meeting [link
-boost_asio.requirements.Handler handler] requirements as the final parameter.
+boost_asio.reference.Handler handler] requirements as the final parameter.
These handlers accept as their first parameter an lvalue of type `const
error_code`.
@@ -110,7 +110,7 @@
`asio_handler_deallocate()`, and `asio_handler_invoke()` calls to the
corresponding functions for the user-supplied handler. A bound completion
handler meets the requirements for a [link
-boost_asio.requirements.CompletionHandler completion handler].
+boost_asio.reference.CompletionHandler completion handler].
For example, a bound completion handler for a `ReadHandler` may be implemented
as follows:
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Boost-cvs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/boost-cvs
