111–119 of 119 posts
Earlier quoted context omitted.
Sourcetrail developer here: Pretty solid. We use clang libTooling.
How's the performance on a large codebase? North of 500k lines, few thousand cpp/h files, 40+mb
A couple of relatively minor comments for you:
* In C++ it might be useful to filter include guards out of the symbol lists.
* I had some problems with using the menus (couldn't click on them, when I did select them couldn't get the menu to drop down). It's probably just because I'm using a weird window manager (xmonad, no window decorations, Ubuntu 16.04).
One (potentially paying) alternative would be to provide a precompilation service. Not sure if your index generation can be parallelized, but potentially you could take an archive of the code (or pull directly from Github or Bitbucket or any other repo endpoint) then spin up a large EC2 instance (or the equivalent for your cloud of choice) and accelerate the generation of the index. For large codebases it may provide a good boost.
Earlier quoted context omitted.
C# please!
Um..you already have this if you have visual studio 2015. https://youtu.be/01MzfE8s6G8?t=54
Do you also have arrows to methods in your own class? In addition, how does this relate to code maps in VS? https://msdn.microsoft.com/en-us/library/jj739835.aspx Seems they cover a similar thing.
Yes, Sourcetrail also shows class internal calls and accessed fields. Code Maps in VS has a different approach because they try to keep the graph small by making the user add symbols. So if you are trying to see every access of a symbol it is easy to miss something. Sourcetrail on the other hand keeps the graph small and comprehensible by showing only one level of dependencies. You don't need to add anything yourself…
I now notice the free trial cannot be run on your own project. I have to say I won't buy anything that I didn't try on a real sample before. What made you decide to go for this option instead of regular limited functionality or time bound (my preference).
Earlier quoted context omitted.
Yes, Sourcetrail also shows class internal calls and accessed fields. Code Maps in VS has a different approach because they try to keep the graph small by making the user add symbols. So if you are trying to see every access of a symbol it is easy to miss something. Sourcetrail on the other hand keeps the graph small and comprehensible by showing only one level of dependencies. You don't need to add anything yourself…
Thanks. Sounds more promising than I took from you landing page. I will give it a go on my c/c++ code bases. See if it can help me. I now notice the free trial cannot be run on your own project. I have to say I won't buy anything that I didn't try on a real sample before. What made you decide to go for this option instead of regular limited functionality or time bound (my preference).
Earlier quoted context omitted.
Thanks. Sounds more promising than I took from you landing page. I will give it a go on my c/c++ code bases. See if it can help me. I now notice the free trial cannot be run on your own project. I have to say I won't buy anything that I didn't try on a real sample before. What made you decide to go for this option instead of regular limited functionality or time bound (my preference).
Oh, we have a time bound evaluation testing period available: https://www.sourcetrail.com/trial#test-license
There doesn't seem to be a vscode plugin for Sourcetrail. Could be a worthwhile addition?
Earlier quoted context omitted.
This seems like no better off. Documentation is historically always out of date the second its written. The same would be true for annotation.
As noted by others the annotations would be active checks. More like proofs in coq than static text. That way you'd be building up a logical understanding of the code base that was machine verifiable sidestepping the issue of stale comments. If done properly this could even feed into code dynamics to capture information on the runtime information. So that at every point in the program you could start asking questions…