<br><br><div><span class="gmail_quote">On 09/01/2008, <b class="gmail_sendername"><a href="mailto:pibsid@suomi24.fi">pibsid@suomi24.fi</a></b> <<a href="mailto:pibsid@suomi24.fi">pibsid@suomi24.fi</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;">
As for casting durations or floats to time one should always ask how the newly made time relates to the one(s) we already have?<br>Most logical would be that:<br>minute $ time => time sometime;<br>refered to "one minute after the VM started". But it could also refer to "one minute after this shred started".
<br>I find it more clear syntatically if we had predifined global and local time variables of VMstart and me.start (or me.birth). Then it would be clear from the syntax what is meant.<br><br>VMstart + minute => time sometime;
<br>//As opposed to:<br>me.start + minute => time anothertime;</blockquote><div><br>This makes a lot of sense to me and sounds quite coherent as a plan.<br><br>Sytactically we could add "start" to both the Machine and "Shred" functionality ("me" is a reference to a shred as well)
<br><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;"><br>I'm still thinking for the most effective way of changing the tempo on the fly...
</blockquote><div><br><br>Yeah, that's a tricky one, especially if we have mulptiple intervals going at the same time and want to maintain sync. <br></div><br>Yours,<br>Kas.</div>