[chuck-users] public class connections mystery

[Kassen]

On Mon, Mar 05, 2012 at 09:36:38AM -0800, Robert Poor wrote:
 
> Okay, I get that.  I'm personally happy that ChucK shreds de-allocate
> the resources that they've allocated upon exit, including connections.
>  In your case, perhaps you could create a long-lived "connection
> shred" whose contract is to set up the patches, and let the other
> shreds send messages to it.  That's the basic approach I used in my
> real-time setups.

Interesting. First of all; I prommised to look at this but then
Stuff(tm) came on my path and I had to set priorities. I still mean
to.

More topically; Robert's approach is sound and a interesting way of
dealing with namespace and scope, but it needs events that are static
members of public classes. Name-space-wise those should be the same as
UGens that are static members of public classes so in a strict way
this shouldn't change anything but the syntax for making and breaking
connections. (I think....)

Clearly it would get arround the matter of connections being
potentially unchucked as UGen references disapear so it might help in
practice but I'm not sure that this help is desirable and intended
behaviour.

Yours,
Kas.