Is there a quick way to get a list of all abstractions called within a patch?

Ideally in a recursive way

Thanks

Jim

@JJLloyd I think in future when writing new abstractions I might include a print object that gives its name and $0 number that is loadbang'ed. Then when a patch loads I will get a list of what abstractions being loaded. I did this just now and it helped with tracking down an annoying error as the console reports the $0 number not the abstraction name.

As an aside another useful tool was opening the abstraction in a text editor and searching for the error using the find option.

Also for this reason it's really helpful when people use [libraryname/objectname] when loading objects external to a particular folder, or at least use [declare -stdpath xxx] etc