Hi guys, this is my first report about scanny for #1 week:
http://ruby-blog.pl/GSoC/2012/05/28/scanny-week-1/
-- Piotr Niełacny
http://ruby-blog.pl/GSoC/2012/06/05/scanny-week-2/
-- Piotr Niełacny
On 05.06.2012 10:55, Piotr Niełacny wrote:
Hi Piotr,
Did you look at brakeman[1]? It suprises me not to see a reference to it in your presentation. It would be interesting to know what's lacking in it, so we need a new/different scanner.
I made good experience with it when checking the build service code.
Greetings, Stephan [1] https://github.com/presidentbeef/brakeman
2012/6/5 Stephan Kulow coolo@suse.de:
On 05.06.2012 10:55, Piotr Niełacny wrote:
Hi Piotr,
Hi Stephan, I'm sorry that so long did not answer
Did you look at brakeman[1]? It suprises me not to see a reference to it in your presentation. It would be interesting to know what's lacking in it, so we need a new/different scanner.
Yes. In presentation I mention about syntax-tree-extractor software. For me brakeman is too compiled for such a type of software. I know that there were problems with the transition from Ruby 1.8 to 1.9. In scanny we use Rubinius we can simply use with 1.8 and 1.9 (rubinius team extract parser from MRI implementation). I'll see how the present situation today in this project.
I made good experience with it when checking the build service code.
Greetings, Stephan [1] https://github.com/presidentbeef/brakeman
Week report #3 #4 http://ruby-blog.pl/GSoC/2012/06/18/scanny-week-3-4/
Week report #5 http://ruby-blog.pl/GSoC/2012/06/25/scanny-week-5/
Week report #6 http://ruby-blog.pl/GSoC/2012/07/03/scanny-week-6/
Week report #7: http://ruby-blog.pl/GSoC/2012/07/09/scanny-week-7/
Week report #8: http://ruby-blog.pl/GSoC/2012/07/16/scanny-week-8/
Week report #9: http://ruby-blog.pl/GSoC/2012/07/23/scanny-week-9/
Week report #10: http://ruby-blog.pl/GSoC/2012/07/30/scanny-week-10/
Week report #11: http://ruby-blog.pl/GSoC/2012/08/06/scanny-week-11/
Week report #12: http://ruby-blog.pl/GSoC/2012/08/20/scanny-week-12--final/