[L2Ork-dev] Ad hoc parsers in Purr Data

Ivica Bukvic ico at vt.edu
Fri Mar 23 19:05:46 EDT 2018


I agree, this is not a huge deal. It is more a matter of consistency and
minimizing confusion among the new potential users, which as far as I can
tell is key to growing a community.


-- 
Ivica Ico Bukvic, D.M.A.
Creative Technologies in Music
Director -- DISIS, L2Ork, CTM
ICAT Senior Fellow
Virginia Tech
School of Performing Arts – 0141
Blacksburg, VA 24061
(540) 231-6139
ico at vt.edu
www.performingarts.vt.edu
disis.icat.vt.edu
l2ork.icat.vt.edu
ico.bukvic.net

On Fri, Mar 23, 2018, 19:03 Alexandre Torres Porres <porres at gmail.com>
wrote:

> 2018-03-23 18:58 GMT-03:00 Ivica Ico Bukvic <ico at vt.edu>:
>>
>> Agreed. And if this proves really important to the old-school vanilla
>> users of which I am unsure if we have that many in the pd-l2ork camp, then
>> we can always expose this fix to the -legacy flag until (if) it gets fixed
>> in vanilla.
>>
>
> I can't see how this should be of any concern, actually. I'd like to know
> a practical example where this behaviour should be relied on or important...
>
> anyone?
>
>
> _______________________________________________
> 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/20180323/cd8f29d9/attachment.html>


More information about the L2Ork-dev mailing list