[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [sc-users] Re: top five sclang pet peeves



2017-12-25 22:24 GMT-03:00 <jamshark70@xxxxxx>:
But we don't have a document explaining how to handle "async ops for
dummies" because -- and this is one of my pet peeves -- we only ever
document classes and methods, and we never document important topics that
would be useful to non-computer-scientist users. "Never" -- yes, I'm
overstating, but let's be honest -- I'm not far wrong, am I?

fork {
        var score = Score([
                ...
        ]),
        cond = Condition.new;  // ***
        score.recordNRT(...,
                action: { cond.unhang }  // ***
        );
        cond.hang;  // ***
        ... go on
}

For me it should be even easier than that. Condition and action functions doesn't hide/facilitate enough asynchronous operations. If the user is writing a score its main interest is, and I'll bring something you just said in another thread, oriented towards data and not program flow. Of course a score can be written programmatically taking care of the program flow but that is another (complementary) compositional approach. On the other hand, pattern library have a more declarative approach but its programming interface feels clumsy. I'll try to explain further in the next message (if I can).