Re:Srclib: A polyglot code analysis library
by michaelmior on Thursday August 14, 2014 @07:19PM
(#8180334)
For a tool which is all about being language agnostic, I'm curious why you went with Go struct definitions to define the formats instead of something like JSON Schema[0].
Simplicity and lack of time. :) We'd love to move to something more language-agnostic for the schema definitions. If you're interested, we'd definitely accept a patch.
Re:Srclib: A polyglot code analysis library
by michaelmior on Thursday August 14, 2014 @08:14PM
(#8180472)
Fair reasons :) I'm tied up for the next couple weeks, but I'll keep that in mind for September!
Re:Srclib: A polyglot code analysis library
by diggan on Thursday August 14, 2014 @07:03PM
(#8180286)
Hey! Quick question.
Are looking for the source code to see if you're working on a PHP implementation. Hard to find any links though. Then I started the think, maybe it's not open source at all?
Didn't find any information so, is it open source? In that case, where?
Re:Srclib: A polyglot code analysis library
by adamnemecek on Thursday August 14, 2014 @07:04PM
(#8180290)
There's a Github link on the website right below the email signup
Re:Srclib: A polyglot code analysis library
by adamnemecek on Thursday August 14, 2014 @07:17PM
(#8180324)
Did you guys consider hooking this up with llvm since it provides call graph generation for the supported languages? If so what was the conclusion? If not I might look into it, no promises though.
We haven't looked at llvm yet. None of the tools for the existing languages we've targeted so far (Python, JavaScript, Go, and Ruby) had llvm-based tools that we chose to use. It would be AWESOME to hook it up to llvm. We'll help however we can, if you are interested. I'm [email protected].
Re:Srclib: A polyglot code analysis library
by joshschreuder on Thursday August 14, 2014 @07:30PM
(#8180369)
Looks really awesome! Love the Github and Sublime plugins.
Unfortunately I can't try it out as there doesn't seem to be a Windows version. Any plans for one?
We would love to have Windows support in srclib, but we honestly have no idea what (or how much effort) it would take. It might work in Cygwin as-is. If you or anybody else wants to try it, or at least identify issues, we would help.
One related thing is a lot of folks want to add C# support. I assume that running Roslyn requires Windows, which'd require Windows support for srclib. https://github.com/sourcegraph/sourcegraph.com/issues/157
Re:Srclib: A polyglot code analysis library
by sitharus on Friday August 15, 2014 @01:30AM
(#8181107)
Actually, Roslyn targets Mono as a first-class citizen, so it'll run on any Mono-supported platform :)
Not sure how much progress they've made on that yet though as it's not release ready.
Oh, that is fantastic!
Re:Srclib: A polyglot code analysis library
by dadadadam on Friday August 15, 2014 @10:40AM
(#8182355)
From a quick try, getting it to build from source on Windows requires a minor modifications to task2/logger.go to remove the dependency on syslog and that's about it. But then src.exe toolchain -install-std fails on symlink creation via ln -s C\sourcegraph.com\sourcegraph\srclib-go C\sourcegraph.com\sourcegraph\srclib-go (looks odd btw). No stack trace to chase down to replace that with mklink, but it shouldn't be to hard to trace down.
Ah, thanks for trying this. It's probably making some Unix assumptions in the pathname creation.
Re:Srclib: A polyglot code analysis library
by azmenthe on Thursday August 14, 2014 @08:52PM
(#8180556)
Awesome project! Any timeline on vim support?
None of the original contributors use vim, so we wouldn't make a very good plugin for it. We'll help anyone who wants to make one, feature them on srclib.org (obviously), etc. Do you know anybody who'd be interested in making a vim plugin? A good place to start looking to see what's involved is in the code for emacs-sourcegraph-mode, sourcegraph-sublime, and sourcegraph-atom.
Re:Srclib: A polyglot code analysis library
by couchand on Friday August 15, 2014 @02:12PM
(#8183383)
Sign me up. azmenthe, you want to help?
Someone else was interested, too, over at https://github.com/sourcegraph/sourcegraph.com/issues/107 (@lazywei).
Anyone have feedback about how we're explaining the problem and solution, and the first-run experience of using the editor plugins and the "src" tool? We would LOVE to hear it so we can fix/improve it.