[stk] Potential bug found in DelayA (fwd)

[Hiroko Shiraiwa-Terasawa]

DelayA has bug in it. David found the problem can be avoided calling clear
method just after DelayA constructor. Might be some help for those who
have funny behavior with String class.

Hiroko

-- 
Hiroko Terasawa 
<hiroko@ccrma.stanford.edu>

---------- Forwarded message ----------
Date: Sun, 1 Jun 2003 09:41:51 -0700 (PDT)
From: Gary Scavone <gary@ccrma.Stanford.EDU>
To: Hiroko Shiraiwa-Terasawa <hiroko@ccrma.Stanford.EDU>
Cc: Patty Huang <pph@ccrma.Stanford.EDU>
Subject: [stk] Potential bug found in DelayA (fwd)

Hi Hiroko,

I think you ran into the bug just reported by Ryan (see below).  
Sorry.  I'll try to fix these things in the next week or so, but they
won't be implemented around CCRMA until the summer.

--gary

---------- Forwarded message ----------
Date: Fri, 30 May 2003 22:04:49 -0700
From: Ryan Cassidy <rcassidy@stanford.edu>
Reply-To: ryanc@ieee.org
To: 'Gary Scavone' <gary@ccrma.Stanford.EDU>
Subject: [stk] Potential bug found in DelayA

Dear Gary,
 
Think I found a problem with the second (non-default) constructor of the
DelayA module.  As shown in the program listing of your web
documentation 
(http://www-ccrma.stanford.edu/software/stk/DelayA_8cpp-source.html),
the variable apInput is not initialized to zero in the second
constructor.  This causes problems for a call to nextOut() right after
object creation, for example.
 
Cheers, rjc.
--
Ryan Cassidy
Electrical Engineering Graduate Student
Stanford University
E-mail: ryanc@ieee.org