Hi Julian,
In this case, I would lean towards the array as this is being used
to support multiple responses on the same callback.
(Not that it matters that much.)
well, I can imagine that there could be other uses.
to ask back: what would you want to do with the array functionality?
RJK
On Dec 7, 2008, at 7:54 AM, Julian Rohrhuber wrote:
Hi Julian,
Interesting, where do you end up using that capability?
Hi Ron,
today, I'd consider it conceptual purity, of which I hope that it
contributes to a general uniformity. So no musical use case yet. I
found it more worthwile to have a function that can be added to
than to have an array that can be evaluated with one single message.
RJK
On Dec 6, 2008, at 3:11 PM, Julian Rohrhuber wrote:
BTW: this looks identical to what you do to handle
uninitialized Arrays. So couldn't
FunctionList be directly derived from Array rather than as a
container of an Array?
we have no multiple inheritance. When I wrote it I found it more
important that it works like a Function, so it is a subclass of
AbstractFunction.
a = FunctionList([{ 1.0.rand }, { 1000.rand }]) + { [2, 5,
7].choose };
a.value
--
--
.
_______________________________________________
sc-dev mailing list
info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: https://listarc.bham.ac.uk/marchives/sc-dev/
search: https://listarc.bham.ac.uk/lists/sc-dev/search/
_______________________________________________
sc-dev mailing list
info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: https://listarc.bham.ac.uk/marchives/sc-dev/
search: https://listarc.bham.ac.uk/lists/sc-dev/search/
--
.
_______________________________________________
sc-dev mailing list
info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: https://listarc.bham.ac.uk/marchives/sc-dev/
search: https://listarc.bham.ac.uk/lists/sc-dev/search/