hello henning (& list)
thanks, i appreciate that there are alternative notations, but all of
these still require introducing/binding a 'temporary' name to a value
that is only used once. that is what i find clumsy. i understand
that the notation i'm wondering about is not trivial to implement and
may lead to odd error messages. however i'm hoping someone either
knows a solution or an explanation of why it'd be a bad idea!
bests
rohan
ps. my growing inclination for hsc3 is to use the non-monadic
(explicit id) notation with a class constraint for the id so that
people can use characters, or integers, or strings, etc. etc.
ie.
let { n = lpf (brownNoise 'α' AR) f * m + a
; ff = onePole (brownNoise 'β' AR) 0.99 }
in rhpf n ff 0.03 * g
however this has the obvious drawback of making graphs non-composable
when abstracted without explicitly 'composing' identifiers, ie.
mk id f m a g =
let { n = lpf (brownNoise (id `mappend` 'α') AR) f * m + a
; ff = onePole (brownNoise (id `mappend` 'β') AR) 0.99 }
in rhpf n ff 0.03 * g
_______________________________________________
haskell-art mailing list
[email protected]
http://lists.lurk.org/mailman/listinfo/haskell-art
