I think the information you want is only available at runtime. Look at the GETDATABASE function. It would be the best place to capture dynamic lookups.
Looking up a function and finding the implementation either at the domain or category level is a complex process. At any time in the future someone can add / change a domain / category which will change the graph. You'll probably have to generate a new graph with every system build or, at least, every algebra change. Trying to discover this information from static *.daase files is basically writing a new compiler, which would naturally require implementing large portions of the interpreter. The Aldor effort was supposed to create a new compiler before it went off the rails into a new programming language. This is the reason my new version is pure Common Lisp. Creating the tool you want is probably a one-day coding effort. On Saturday, September 21, 2024 at 7:19:46 AM UTC-4 oldk1331 wrote: > > > On 9/21/24 7:17 PM, Tim Daly wrote: > > Quan, > > > > One suggestion for finding dependencies is to turn on autoload messages. > > Starting from a clean image you can find the list of domains that need to > > be autoloaded. Choosing one of the listed domains you can apply the same > > technique to see what it requires. > > > > I wonder if it is possible to get those dependencies from the static > *.daase files (aka the database). > > - Qian > > -- You received this message because you are subscribed to the Google Groups "FriCAS - computer algebra system" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/fricas-devel/94ed3e04-7c6d-43f1-a5dd-05cd21387ccdn%40googlegroups.com.
