
I had in mind some samples of 'stuff' sent to cout, including the input arguments if appropriate. You could follow many other Boost examples and add the output at the end of the examples as a comment: /* Output is: ... ... */ This avoids having to build the code to try it or confirm ones understanding of what the examples do(though this could be a good idea if looking at it in detail of course). (The intro is good). Paul Paul A Bristow Prizet Farmhouse, Kendal, Cumbria UK LA8 8AB +44 1539 561830 +44 7714 330204 mailto: pbristow@hetp.u-net.com | -----Original Message----- | From: boost-bounces@lists.boost.org | [mailto:boost-bounces@lists.boost.org] On Behalf Of Pedro LamarĂ£o | Sent: 07 July 2005 20:50 | To: boost@lists.boost.org | Subject: Re: [boost] [network] Boost.Network proposal v0.2 | | Paul A Bristow wrote: | | >I agree, but it would be more immediately compelling if the | impressive | >examples provided some sample output(s) so we can quickly | see it in action. | > | > | Well... The "client" examples throw stuff to cout, and the "server" | examples are primitive Internet protocols usable with telnet. | | What kind of sample output are we talking about? | A step by step "verbose" mode? | | -- | Pedro LamarĂ£o | Desenvolvimento | | Intersix Technologies S.A. | SP: (55 11 3803-9300) | RJ: (55 21 3852-3240) | www.intersix.com.br | | Your Security is our Business | | | | _______________________________________________ | Unsubscribe & other changes: | http://lists.boost.org/mailman/listinfo.cgi/boost |