[chuck-users] current bug summary (partial, obviously)
joerg at piringer.net
Wed Jun 28 02:05:13 EDT 2006
i'd need to capture both outputs (<<< >>> & chuck log).
the winxp fprintf to stderr doesn't flush or send the output to the
capturing program before chuck is exited.
my tool captures the output to trace the status of the virtual machine
so i can add, remove and replace shreds in an audicle-style manner.
works fine, but only with stderr flushed. i can post my tool for testing.
so actually yes: i'd need fflush for all outputs.
Ge Wang wrote:
> Done. It will be in the next release. Now in CVS.
> (Note: the log output is still as it was; only <<< >>> is now flushed -
> let us know if more flushing is required)
> On Jun 27, 2006, at 7:03 PM, joerg piringer wrote:
>> and please:
>> flush stderr after each fprintf. on winXP systems this is neccessary.
>> that makes it possible for my tool to capture the chuck output during
>> Ge Wang wrote:
>>> Hi all!
>>> Here is quick summary of some bugs/features recently discussed.
>>> bugs - to be fixed by 220.127.116.11 or earlier.
>>> 1. --/++: incorrect behavior when used inline
>>> 2. sporking non-static member functions: this doesn't or at least
>>> shouldn't work - we are on it
>>> 3. declaring multiple variables: float a, b, c; causes incorrect
>>> 4. static variables of classes (another long standing bug)
>>> missing features, in addition to the usual ones (strings etc.):
>>> 1. iterating over contents of associative arrays
>>> 2. multiple class declarations over time (a better way to deal with
>>> classes on-the-fly)
>>> 3. on-the-fly replacement by name (when possible)
>>> 4. better sndbuf for stereo/multichannel playback
>>> chuck-users mailing list
>>> chuck-users at lists.cs.princeton.edu
>> chuck-users mailing list
>> chuck-users at lists.cs.princeton.edu
> chuck-users mailing list
> chuck-users at lists.cs.princeton.edu
More information about the chuck-users