[chuck-users] class confusion

[Kassen]

On 7/11/06, Ge Wang <gewang at cs.princeton.edu> wrote:
> Hi Atte,
>
> The example you provided reveals a bug in chuck: order of declaration
> mattering when it should not.  It's now noted to be fixed.  Sorry for
> the confusion.

There are more problems of that type. If you have some sporked
function that chucks some value to a parameter of a ugen and you
define the ugen below the function it will compile, then crash the VM
as soon as the sporked function tries to write to the parameter.

I can't remember seeing that mentioned but it happens to me a lot if
I'm not carefull. IMHO correct behaviour would be simply "swalowing"
that order of declaring stuff. The one case (as far as I can see)
where that could run into issues if we would declare two ugens the
same name but the VM already files a complaint if we do that.
Currently I need to have a block labeled "define stuff before refering
to it" at the top of my files. Admittedly this is "correct" in a way
but it does lead to stuff getting defined far away from it's context
which leads to hard to read and hard to debug constructions.

Kas.