I was wondering if any thought has been given to being able to run both the cppcheck parser and the clang parser and send the results back with donate-cpu.py?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
yes I think that will be interesting in the long run. I believe it's still not working very well and we have a lot of issues to solve first before the comparison would be interesting. right now there would likely be too much output..
I probably do not want to force that people install clang so it should probably be an optional step.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yeah I was thinking of starting small.
1. See if I could get donate-cpu.py to see if they already have clang installed.
2. Try to better understand the the cppcheck/clang parser comparison short falls.
3. Maybe create a small white list of a few packages to try it out on. I think it was on one of your kickstarts that you did on libcurl a while back. Do you have any recommendations of packages to try it on?
I have no doubt that it is a long development road to go down, but I was thinking maybe a small amount of automation might help preserve some of the baby steps along the way.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
feel free to take some baby steps. I don't feel I can recommend good packages.. but I'd guess it's a good idea to start with pure C projects only. Feel free to pick some C++ project that looks interesting also..
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I was wondering if any thought has been given to being able to run both the cppcheck parser and the clang parser and send the results back with donate-cpu.py?
yes I think that will be interesting in the long run. I believe it's still not working very well and we have a lot of issues to solve first before the comparison would be interesting. right now there would likely be too much output..
I probably do not want to force that people install clang so it should probably be an optional step.
Yeah I was thinking of starting small.
1. See if I could get donate-cpu.py to see if they already have clang installed.
2. Try to better understand the the cppcheck/clang parser comparison short falls.
3. Maybe create a small white list of a few packages to try it out on. I think it was on one of your kickstarts that you did on libcurl a while back. Do you have any recommendations of packages to try it on?
I have no doubt that it is a long development road to go down, but I was thinking maybe a small amount of automation might help preserve some of the baby steps along the way.
feel free to take some baby steps. I don't feel I can recommend good packages.. but I'd guess it's a good idea to start with pure C projects only. Feel free to pick some C++ project that looks interesting also..