<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
As suggested in option 2. below, an optional ostream argument has
been added to the Forward function; see the heading 08-10 on<br>
<a class="moz-txt-link-freetext" href="http://www.coin-or.org/CppAD/Doc/whats_new_11.htm#08-11.08-10">http://www.coin-or.org/CppAD/Doc/whats_new_11.htm#08-11.08-10</a><br>
<br>
On 8/5/2011 7:02 AM, Iakov Nakhimovski wrote:
<blockquote
cite="mid:CAM9q8UpHL-VOwHn0Pok24Rh0DaROZw4Ouev7snt5XrF1meCwOQ@mail.gmail.com"
type="cite">
<pre wrap="">Hello!
I’d like to propose support for custom output streams to be used with
PrintOp. Right now all the messages go to std::cout which is not
convenient in the case of DLL potentially run in multithreaded
context.
To enable the support I’d suggest either:
1. Adding ostream& to ADFun<Base> and player<Base> classes
complemented with appropriate set/get on the ADFun (default is
cstd::cout).
2. Optional ostream* parameter for “Forward” to be forwarded into
forward_sweep/forward0sweep (instead of the bool print). The parameter
is then propagated to PrintOp and used for printing (NULL pointer = no
output).
Thanks in advance!
/Iakov
</pre>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
CppAD mailing list
<a class="moz-txt-link-abbreviated" href="mailto:CppAD@list.coin-or.org">CppAD@list.coin-or.org</a>
<a class="moz-txt-link-freetext" href="http://list.coin-or.org/mailman/listinfo/cppad">http://list.coin-or.org/mailman/listinfo/cppad</a>
</pre>
</blockquote>
<br>
</body>
</html>