Well, I don't know, it seems to me that use cases where the declaration order matters (name clash, overloading...) are relatively rare, so it's rarely needed to concatenate more than a couple of paths. So maybe the index argument would be overcomplicated.
I can say the same as Roman: I'm personally quite happy with the [declare] system as it is now!
However, old patches that used "-stdpath" don't work on newer setups, where externals are no longer stored in "standard" directories. Are "-stdpath" and "-stdlib" still absolutely necessary today? If they weren't, they could be made equivalent to "-path" and "-lib" so every choice would work. Maybe a startup flag could then restore the original behavior, if needed.
Antoine Rousseau http://www.metalu.net http://metalu.net __ http://www.metaluachahuter.com/ http://www.metaluachahuter.com/compagnies/al1-ant1/
Le jeu. 25 févr. 2021 à 20:59, Dan Wilcox danomatika@gmail.com a écrit :
(reposting with correct subject line)
Perhaps [declare] needs an order index argument, similar to [gemhead #] to clearly specify order when required?
On Feb 25, 2021, at 12:00 PM, pd-list-request@lists.iem.at wrote:
Perhaps for use with "nested" code, use of abstractions, possibly in other abstractions etc.
yes and it would be better readable than a long list of "-path ..."s with linebreaks ...
Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com robotcowboy.com
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list