David Abrahams wrote:
David Abrahams <[EMAIL PROTECTED]> writes:
We have examples whose correctness can only be tested well by
verifying that they produce a particular output on stdio. Standard
code testing stuff.
Actually there's a little more than that. The book says something
like:
With this code example
int main()
{
int x;
std::cin >> x;
std::cout << ("hello world!" + x) << std::endl;
}
the input
4
produces
o world!
on the standard output.
Now can you see why one might want to check that the example produces
particular output? In this case, the expected output is actually
contained in the documentation.
Indeed! Now I'm beginning to understand. Cool! This is
exactly what I am looking for. Thanks for the use case.
Examples *do* say a thousand words.
Regards,
--
Joel de Guzman
http://www.boost-consulting.com
http://spirit.sf.net
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Boost-docs mailing list
[email protected]
Unsubscribe and other administrative requests:
https://lists.sourceforge.net/lists/listinfo/boost-docs
