<br><br><div><span class="gmail_quote">On 8/29/07, <b class="gmail_sendername">Martin Ahnelöv</b> <<a href="mailto:operagasten@gmail.com">operagasten@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>You should be able to $ chuck + foo bar - 1 2 3 = 4 foobar. Nuff said.</blockquote><div><br>Could you perhaps still say a little more? I don't understand this at all, I fear.<br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On the same topic, you should be able to $ chuck -3, because it's a pain<br>in the ass to forgett the space =)</blockquote><div><br>Hmmmmmm. Not so sure, because "-3" is also a number.<br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Also, $ chuck <a href="http://foobar.ck">foobar.ck</a> shouldn't break a VM.</blockquote><div><br>You are quite right, any time that can happen that's a serious bug. <br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Now, more language wise:<br><br>a .cycledur on (at least) the oscillators. Sometimes you just want to<br>tell the machine how long time a lfo's cycle should be, instead of<br>having to do hard calculating =)</blockquote>
<div><br>We have this already :-). What we need is better documentation on it.<br>It's called ".period()" for the oscilators and the type is duration.<br><br>It was new in <a href="http://1.2.0.7">1.2.0.7</a>
and got mentioned in the "wat's new?" file but the manual hasn't caught up yet.<br>I like this one, it's a very logical extention to ChucK's emphasis on time and timing.<br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
And a dur => blackhole; would be neat, too. Ie, you forward the shred<br>dur samples in time. That's isn't too processor-intense to calculate,<br>right?</blockquote><div><br>Could you give a example of what this would do? How would this be different from "dur => now;"?
<br> </div>Yours,<br>Kas.<br></div>