[chuck-users] chout and cherr confuse me [BUG?]
rdpoor at gmail.com
Tue Oct 20 18:52:54 EDT 2009
I'm not the expert, but I'm pretty sure that you can expect ChucK's
handling of stdout vs stderr to be exactly the same as <insert
favorite OS here>. I believe that printing to stdout gets flushed
more aggressively than printing to stdout, but the flip side is that
printing to stdout is overall more efficient. (That's why you see
cherr output appear before chout.)
But the bottom line: if you've been happy with the way printing to
stdout and stderr works your OS works, you'll be fine with ChucK.
On 20 Oct 2009, at 15:42, Kassen wrote:
> I don't think it will ever take that long to print something.
> Well, my issue is that here it takes as long as the next usage
> before it prints, that might be 10::hour.
> Did you run my example script? First usage gives me three lines of
> output, from there on 4 with the first chout line being the last
> chout call of the previous time I ran it. This is the latest Mini
> (+CNoise fix) in Alsa mode on the latest LTS of Ubuntu. cherr calls
> are independant from this, seem to get precedence, and work about
> like you described what I could expect.
> I don't think that's right. Sorry if these exact symptoms weren't
> clear from my last post. Can
> anybody reproduce this?
> chuck-users mailing list
> chuck-users at lists.cs.princeton.edu
More information about the chuck-users