I want to understand how the GLM package works by looking at the source code.
I used the package manager’s develop command to get the code.
I asked for a local install, thinking it would go to my local directory. But instead it’s a few layers down from my Windows “home” directory (~/.julia/…). Is there a way to put it under my project directory? Even if there is, is that a bad idea?
The package makes extensive use of code from other packages. The package manager brought them in automatically, but apparently as binary packages. Which don’t help much if I want to see the source. I could chase through the references by hand and get a develop version of each, but is there are more automatic way to do so?
It may also matter that my intention differs some from that which the package manager develop is designed. The latter is about getting and modifying a package; I only want to browse the source.
- I thought once I had the source code juno would help me with things like lists of types and functions, quick jumping to definitions, references or calls, but the documentation for juno doesn’t seem to mention such features. There is a “go to definition” shortcut which sounded promising, but in my limited attempts it didn’t do anything. Possibly this is caused by 1 or 2 (more likely 2–it obviously can’t show the source if there is no source available), or by the fact that I hadn’t loaded any of the modules since I just wanted to browse the source. What tools can be helpful in understanding and navigating source code from several modules?