Thought it would be better to reopen this on another branch. Basically waiting for instructions now.

I think I've now figured out how to do this but I do need some direction/decision by more experienced folks as to what exactly to do.

We've agreed on non-breaking changes, i.e., only adding things rather than changing interfaces (i.e., not simply "fixing" the existing trunc). So at any rate, the resulting solution should not break code written in sclang. So that doesn't need to be discussed. The question is really about the Server side only.

There are two main options:

1. Simply add new, "fixed" UGens (truncate and divide)
2. Replace the respective operations with corrected ones, and reimplement the backward-compatible trunc on the class library side.

1 of course is simplest. It just seems a bit inelegant and adds more code. Sort of a shantytown approach.
2 replaces some code in the server and adds very little to the class library.

For 2, there would be 2 options:

• a) Internally rename the operations in question (i.e., opTUGenrunc becomes opTruncate), such that a .truncate method would call a _Truncate primitive).
• b) don't rename them, only correct the math. I think this could become confusing.

Within 1, two more questions:

• a) For truncate, the question is:
  • Should it be a unary or a binary op?
    • if it is to be strictly analogous to sc's trunc , then it would a binary op, with two extra multiplications. (Sc's trunc is currently std::floor(a/b) * b; a binary op truncate would be std::trunc(a/b) *b. )
    • if it is to behave like c-style trunc, then it would be unary.
• b) Should the extra code for that UGen be in a separate file, or at the end of the respective naryOpUGens file?

I think that's roughly it.