But, seriously, the page needs some updating. Under "what's new?" there are examples listed that aren't listed in the examples page--not only that, but one is misspelled! ("examples/array/array_dyanmic.ck"). So, basically, this is exactly what I want to do, but it requires some spelunking gear and a frustrating amount of time to figure out.

Also, there are a bunch of new UAnae, I see? I'm not really sure where to go to see what they do, though. Hey guys, I like this language, but there needs to be some serious documentation work, even to the level of "this exists." If you (anyone) want, contact me off-list and I can work on it. I don't really know what's going on with the programming thing, but I'm an English major with good InDesign/web skills and could provide the site with some updated pages. I'd love to be able to learn this stuff, just because of the way that ChucK makes you think differently than, say, Max/MSP where you just need a [notein] and you've got easy (boring) MIDI synths. Okay, enough soliloquizing, get ChucKing.

On Tue, Apr 28, 2009 at 4:04 AM, Kassen <signal.automatique@gmail.com> wrote:

Andrew;

> Where is the documentation for this stuff?

The honest answer is probably "Scattered over /examples/, the manual,
the online docs, the VERSIONS file and with the errata in the list
archives", like all of the other docs. I feel we should consider this
is a good thing; you'll have to look for a while but you'll also find
all of these other things that are also nice and stimulating ;Ź).

For arrays the best place right now is probably the VERSIONS file as
the last update added significant additions, I think those are also
demonstrated in /examples/arrays. (Second basement, bottom left
corridor, up the stairs, third shelf, below the skull. Bring a candle
and beware of the cat...)

You may want to beware as right now there are serious issues with
arrays and the type system. I really hope we'll get a speedy fix for
those; it used to be exciting to hunt for them but now it's been
enough, I feel. It'd be nice if the DEV's could spare some time to
comment on whether that issue (or those issues) have now been
documented in sufficient depth to pinpoint and fix the cause.

Cheers,
Kas.
_______________________________________________
chuck-users mailing list
chuck-users@lists.cs.princeton.edu
https://lists.cs.princeton.edu/mailman/listinfo/chuck-users