[chuck-users] chout and cherr confuse me [BUG?]
silvestre.toth at gmail.com
Wed Oct 21 08:26:43 EDT 2009
Maybe I missed something on the web site, but I could not find a list for
the fixed bugs that'll probably be included in the next release (including
your "hot" fixes for std* streams).
Is there a "coming soon" feature list somewhere?
Szilveszter aka Hillaby
2009/10/21 Ge Wang <ge at ccrma.stanford.edu>
> Alright! I am happy to report that both .flush() and IO.newline() and "\n"
> triggering flush on chout has been fixed/implemented (I think), along with a
> number of associated "features" fixed. The code is in CVS and will be
> released with the next version, which we might just release soon!
> Thanks again Kassen and all!!
> On Wed, 21 Oct 2009, Kassen wrote:
> Hi, Szilveszter!
>> I fear that this has to do with buffering (whether a stream is
>> buffered or not), and if buffered, buffer size makes a
>> difference, too.
>> For example, in C/C++, if you want to see the output of a
>> fprintf() call for sure, you have to call fflush(). I don't know
>> if it has a ChucK equivalent, though.
>> Ah, we're getting there! This, combined with Ge's last mail and my own
>> report on chout.flush() crashing is going to fix it, or so I hope.
> chuck-users mailing list
> chuck-users at lists.cs.princeton.edu
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the chuck-users