[L2Ork-dev] Ad hoc parsers in Purr Data

[Ivica Bukvic]

Time permitting I can try to tackle the former.


-- 
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:48 Jonathan Wilkes <jon.w.wilkes at gmail.com> wrote:

> On Fri, Mar 23, 2018 at 7:05 PM, Ivica Bukvic <ico at vt.edu> wrote:
> > 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.
>
> Part one of attacking that problem is understanding what our codebase does
> and running tests to make sure it stays that way.
>
> That's why I am attempting to enumerate the parts of the code where
> inconsistencies are likely.
>
> Now that my topic for this thread has been preempted by a discussion
> about a bug neither Albert nor I want to prioritize, who is going to
> take ownership
> for fixing the bug?
>
> And who is going to make a good faith effort to port the fix into
> Vanilla so that
> we try to maintain compatibility?
>
> -Jonathan
> _______________________________________________
> 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/8799c9c9/attachment-0001.html>