A full call graph would be great. Between the profiler and code-coverage (try `julia -h` if you don't know about code-coverage), you can at least get close.
Obviously the debugger, when that lands, will be the nicest tool of all. --Tim On Tuesday, September 09, 2014 09:16:05 AM Andreas Lobinger wrote: > Hello colleagues, > > the obvious answer to the literal question is: Open the file and use your > favorite method of text-to-mind-transfer. > > However, the question goes deeper: Are there tools available that help me > (or anyone) understanding a given program structure? > > More than once now, i thought: Well, extending that package should be easy, > but later it was medium sized complicated, as the program structure was > somehow hidden inside a type hierarchy. And just a call graph would have > been nice. > > In other environments i'd use a debugger (and some breakpoints) or some > tools for tracing. Or the find function in the text editor. > In Julia programs due to multiple dispatch the function name tells me only > half of the story which part of the source to read, i need the type of the > argument also. > > I played around with the Profiler, but as it is sampling, not all the > called code is showing up. > > Do i miss something obvious for tooling? > > Wishing a happy day, > Andreas
