e&amp;</code>; whereas we combine the two via the <code>Error_code*</code> null-vs-not dichotomy. (It's redundant, because it's just following the Flow pattern.)</p>
<p >Lastly, <code>Peer_socket::send()</code> is identical to <code>Peer_socket::write_some()</code> but adds an overload wherein one can pass in a (largely unportable, I (ygoldfel) think) <code>message_flags</code> bit mask. We do not provide this feature: again because it is not needed, but also because depending on the flag it may lead to une