[L2Ork-dev] list cat

[Ivica Bukvic]

Considering it is fairly easy to do, we may want to make an alias for list
store as list cat to prevent breaking older code.

Best,

Ico

-- 
Ivica Ico Bukvic, D.M.A.
Director, Creativity + Innovation
Institute for Creativity, Arts, and Technology

Virginia Tech
Creative Technologies in Music
School of Performing Arts – 0141
Blacksburg, VA 24061
(540) 231-6139
ico at vt.edu

www.icat.vt.edu
www.performingarts.vt.edu
l2ork.icat.vt.edu
ico.bukvic.net

On Mon, May 13, 2019, 12:50 Jonathan Wilkes <jon.w.wilkes at gmail.com> wrote:

> > On Sun, May 12, 2019 at 11:05 PM Ivica Ico Bukvic <ico at vt.edu> wrote:
> >
> >
> > On 5/12/2019 10:54 PM, Jonathan Wilkes wrote:
> > > On Sun, May 12, 2019 at 10:39 PM Ivica Ico Bukvic <ico at vt.edu> wrote:
> > >>
> > >> On 5/10/2019 5:16 PM, Jonathan Wilkes wrote:
> > >>> On Fri, May 10, 2019 at 1:38 PM Ivica Bukvic <ico at vt.edu> wrote:
> > >>>> My understanding is if something has only one argument, at least in
> pd-l2ork, it should be reformatted as a single argument rather than a list.
> Otherwise handling outputted arguments becomes inconsistent and
> problematic. Also, remember when you start adding arguments into an empty
> list cat, the first argument added will be just an argument until another
> one is added at which point it becomes a list.
> > >>> I'm not sure I understand. Do you have an example?
> > >> Thinking here off top my head. Have list cat and add into it a single
> > >> arg (e.g. "blah"). It should output "blah" on bang or whatever
> triggers
> > >> output, as opposed to "list blah".
> > > Ok, got it.
> > >
> > > It appears that [list store] performs significantly better than [list
> > > cat]. So what I might
> > > do is just make a wrapper abstraction to implement "list cat" around
> > > "list store." That will
> > > clean up the code a bit and probably still perform as well as the
> > > current C code.
> > >
> > > I've now got some tests for list cat so it shouldn't be too difficult.
> > >
> > > -Jonathan
> >
> > Sounds good. Thank you for that, Jonathan. One thing to also think
> > about, I used list cat extensively in L2Ork where I wanted to optimize
> > network packet distribution by coupling a bunch of args into a single
> > "send <list of args>" message and this is where list cat would group
> > sometime up to several dozen arguments in a single interrupt/cycle,
> > meaning it would do so recursively during the same cycle. This is a case
> > we may also want to consider.
>
> Recursively or iteratively? It didn't appear to me that [list cat]
> worked recursively.
> But I did make a test for recursion. And I think [list store] handles
> recursion
> properly-- if it doesn't I now have a test for recursion which will
> catch the problem.
>
> -Jonathan
>
> >
> > Best,
> >
> > Ico
> >
> > > _______________________________________________
> > > L2Ork-dev mailing list
> > > L2Ork-dev at disis.music.vt.edu
> > > https://disis.music.vt.edu/listinfo/l2ork-dev
> >
> > --
> > Ivica Ico Bukvic, D.M.A.
> > Director, Creativity + Innovation
> > Institute for Creativity, Arts, and Technology
> >
> > Virginia Tech
> > Creative Technologies in Music
> > School of Performing Arts – 0141
> > Blacksburg, VA 24061
> > (540) 231-6139
> > ico at vt.edu
> >
> > www.icat.vt.edu
> > www.performingarts.vt.edu
> > l2ork.icat.vt.edu
> > ico.bukvic.net
> >
> > _______________________________________________
> > L2Ork-dev mailing list
> > L2Ork-dev at disis.music.vt.edu
> > https://disis.music.vt.edu/listinfo/l2ork-dev
> _______________________________________________
> L2Ork-dev mailing list
> L2Ork-dev at disis.music.vt.edu
> https://disis.music.vt.edu/listinfo/l2ork-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://disis.music.vt.edu/pipermail/l2ork-dev/attachments/20190513/1900e5c6/attachment.html>