<div dir="ltr">2008/7/24 Stephen Sinclair <<a href="mailto:radarsat1@gmail.com">radarsat1@gmail.com</a>>:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><br></div>I *was* kind of curious how you came up with this case.. ;-)<br>
</blockquote><div><br>:¬) I'd explain more but it's a part of a interface revision of a 2500 or so line file so that would quickly get complicated and require a lot of explaining.... Of course anything that would run into this can also be re-written.<br>
<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
I wonder if it wouldn't be better to have the compile issue an error<br>
on something like if(second), since I don't see how it's very useful<br>
and could lead to bad logic on the part of the user. </blockquote><div><br>Well, it's convenient for things like this;<br><br>while (beat => now)<br> {<br> my_drum(boom);<br> }<br><br>...which is arguably bad form but very pleasant to write. I forgot who came up with it but it's popular in the "one line ChucK crazy" game on the forum.<br>
<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> if(!now) could<br>
be useful for doing something only when the VM first starts up,<br>
however I generally think that basing your scripts on absolute time<br>
(relative to start of VM) is probably bad practice. Not to mention<br>
that if(!now), while nice and compact, is not the most readable way to<br>
express that logic.</blockquote><div><br>It's also invalid because "now" is not a integer and you can only do "not" on integers. If you want that you will have to go;<br><br>if ( !((now / samp) $ int) ) <<<"yay">>>;<br>
<br>First the division creates a float, we cast that to integer and this int can be inverted logically. That is, BTW, a issue with inversion, not with evaluating if clauses as such. I use that sort of thing too toggle Gain's used as routing gates;<br>
<br>Gain g;<br><br>//toggle<br>!( g.gain() $ int) => g.gain;<br><br>Ok, well, maybe it's a similar kind of case... after all. Perhaps "!" simply should return "1" for non-zero inputs.<br><br>Beware, BTW, that the above examples aren't without danger because you can have rounding errors casting to int. I think casting to int will always round towards 0.<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
On second though, if(dur) could have some uses, I guess. Not sure.<br>
Perhaps in calculating a delay length, while trying to avoid<br>
zero-delay feedback.<br>
<div></div></blockquote><div><br>There I's use;<br><br>if (delay > 0::ms) <br></div></div><br>Because of the dengers of negative delay.<br><br>While going over Ge's paper, BTW, I sugested that we could perhaps use "unless" as a miror of "if" since we already have "while" and "untill" which are also mirror.images. I intended this as fun syntactic sugar (like "untill" already is) but now that I think of it; that would nicely get around logic inversion of time and dur type variables in many cases.<br>
<br>Interesting discussion; once more it's more complicated then I realised at first.<br><br>Yours,<br>Kas.<br></div>