this is really the same path as found in #560 (so don't apply it double); it makes [declare] do it's thing when created manually (outside of patch-loading), so the new paths/libs have an immediate effect (no need to re-load the patch to use the declarations)
this one prevents [declare] to infect the parent abstractions. it does so by simply not recursing upwards when it encounters an abstraction (instead of a subpatch)
Won't 0002 have a downside effect ?
Currently you can nest a list of [declare]s inside of an abstraction, that you can use as a macro-declare block in application patch. Will this still possible ?
If not, what would you think of adding a flag to [declare], like "-parent" or "-up", restoring the original behaviour, for this special case?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
indeed, this "ab(use)" case won't be possible any more.
otoh, i think it mostly shouldn't be needed as i think this trick is mostly needed to declare sub-dependencies (dependencies within the abstractions) and those abstractions should now declare their dependencies themselves.
btw, both patches have already been accepted into the mainstream Pd repository (no release yet).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
abstractions should now declare their dependencies themselves.
Ok ; but anyway I found it handy to macro-declare many subdirs then being able to create abs in a simple way (without having to prepend path : [e] instead of [a/b/c/d/e] ). That's not such a big deal but adding this kind of flag "-up" could keep this possible.
(sorry for previous anonymous posting, didn't see I wasn't logged in...)
Last edit: Antoine Rousseau 2016-02-25
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
i had already done this as prep for the previous patch
View and moderate all "patches Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Patches"
Won't 0002 have a downside effect ?
Currently you can nest a list of [declare]s inside of an abstraction, that you can use as a macro-declare block in application patch. Will this still possible ?
If not, what would you think of adding a flag to [declare], like "-parent" or "-up", restoring the original behaviour, for this special case?
indeed, this "ab(use)" case won't be possible any more.
otoh, i think it mostly shouldn't be needed as i think this trick is mostly needed to declare sub-dependencies (dependencies within the abstractions) and those abstractions should now declare their dependencies themselves.
btw, both patches have already been accepted into the mainstream Pd repository (no release yet).
Ok ; but anyway I found it handy to macro-declare many subdirs then being able to create abs in a simple way (without having to prepend path : [e] instead of [a/b/c/d/e] ). That's not such a big deal but adding this kind of flag "-up" could keep this possible.
(sorry for previous anonymous posting, didn't see I wasn't logged in...)
Last edit: Antoine Rousseau 2016-02-25