[L2Ork-dev] Patch private abstractions

Jonathan Wilkes jon.w.wilkes at gmail.com
Mon Aug 17 22:01:51 EDT 2020

On Mon, Aug 17, 2020 at 6:10 PM Guillem Bartrina
<guillembartrina at gmail.com> wrote:
> Hi,
> > Is there 1002 hard-coded into the file?
> Yes
> > If there are ten instances of ab two are there ten separate definitions for this counter?
> Yes, because they may differ from one another
> > Do the individual instances necessarily retain their $0 IDs across reload?
> No
> This is a big problem that I completely overlooked. Since the instances don't retain their $0 ID across reload I have to think of a solution right now. Perhaps the solution will be related to making 'local' [ab]s actually local. I have to think about it more.
> -----
> Regarding Jonathan's message. I will read it carefully tomorrow.

Basically, the point is that file-level abstractions are an excellent
tool for delineating the scope of [ab] names.

So the question is if we can find another tool that provides that
functionality of delineating the scope without
require saving a separate file. E.g., something like a [pd] subpatch
that has its own gl_env. Or perhaps a different creator
for [ab] that sets a flag to have its own gl_env.


> Best,
> _______________________________________________
> L2Ork-dev mailing list
> L2Ork-dev at disis.music.vt.edu
> https://disis.music.vt.edu/listinfo/l2ork-dev

More information about the L2Ork-dev mailing list