moved comment about exceptions a bit up
This commit is contained in:
parent
d8ea41ae37
commit
0a8c26be52
|
|
@ -252,6 +252,10 @@ class MyConnectionHandler : public AMQP::ConnectionHandler
|
||||||
};
|
};
|
||||||
````
|
````
|
||||||
|
|
||||||
|
Even though `ConnectionHandler` methods are not marked `noexcept` explicitly,
|
||||||
|
you are not expected to throw from them, and the behaviour is undefined if you
|
||||||
|
do so.
|
||||||
|
|
||||||
After you've implemented the `ConnectionHandler` class the way you like,
|
After you've implemented the `ConnectionHandler` class the way you like,
|
||||||
you can start using the library by creating a `Connection` object, and one
|
you can start using the library by creating a `Connection` object, and one
|
||||||
or more `Channel` objects:
|
or more `Channel` objects:
|
||||||
|
|
@ -295,9 +299,6 @@ However, this is not strictly necessary. Methods called during a handshake
|
||||||
are cached by the AMQP library, and will be executed the moment the handshake
|
are cached by the AMQP library, and will be executed the moment the handshake
|
||||||
is completed and the connection becomes ready for use.
|
is completed and the connection becomes ready for use.
|
||||||
|
|
||||||
And the last but not least: even though `ConnectionHandler` methods are not
|
|
||||||
marked `noexcept` explicitly, you are not expected to throw from them, and
|
|
||||||
the behaviour is undefined if you do so.
|
|
||||||
|
|
||||||
PARSING INCOMING DATA
|
PARSING INCOMING DATA
|
||||||
=====================
|
=====================
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue