-
Notifications
You must be signed in to change notification settings - Fork 29
cleanup README #358
Comments
Agree. I managed to install pfff but was sad not to find spatch. (I wanted to give it a test on a Java project since Haven't found it yet! Update: We got Coccinelle4J to work. There is also this PR to Spoon for SmPL. |
@gordonwoodhull you should look at the spatch spinoff semgrep.dev, with source at https://github.com/returntocorp/semgrep/ |
Thanks for the pointer! I am looking for a tool for applying fuzzy patches (syntactic or semantic) but it kind of looks like I am a few years too early and these tools aren’t solid yet. semgrep looks very interesting - will consider for future projects! |
An updated README would be really useful, i am trying to build codequery/codegraph and don't understand how to. |
I'll try to make a new OPAM release of pfff, codegraph, codequery, so things will be simpler to install, but I don't have that much free time these days as I'm working full-time on semgrep.dev |
thanks @aryx i discovered this tool through semgrep! I'll try to learn ocaml/opam build process and send a PR with the changes. |
Pfff went through some big refactoring (all the tools used to be in the pfff monorepo) to faciltate the semgrep decelopment workflow, but it complicated the workflow a bit for the other tools |
https://github.com/returntocorp/pfff/blob/develop/changes.txt#039-q4-2019-real-python-parser-a-generic-ast-a-generic-sgrepscheck split off several tools:
It would be good to reflect those changes in README.md to avoid confusion - currently it says:
https://github.com/returntocorp/pfff/blob/develop/README.md#pfff
The text was updated successfully, but these errors were encountered: