I've just tried out reek, which is not a bad little tool... but it
chokes on 1.9 sometimes (the new hash syntax).
flog, which I've used in the past, is the same.
What are the newest/best code analysis tools, in your own
opinion?
Thanks,
Hal
I've just tried out reek, which is not a bad little tool... but it
chokes on 1.9 sometimes (the new hash syntax).
flog, which I've used in the past, is the same.
What are the newest/best code analysis tools, in your own
opinion?
Thanks,
Hal
I've just tried out reek, which is not a bad little tool... but it
chokes on 1.9 sometimes (the new hash syntax).flog, which I've used in the past, is the same.
What are the newest/best code analysis tools, in your own
opinion?
This question came up about three months ago at the nashville ruby meetup.
The short answer is **shrug**. These tools are in need of being updated
for
1.9.x
Main tool that Im aware of that fits your category is brakeman
It is a security vulnerability checker.
Andrew
On Wed, Jul 11, 2012 at 11:17 AM, Hal Fulton <rubyhacker@gmail.com> wrote:
Thanks,
Hal
This question came up about three months ago at the nashville ruby
meetup.
The short answer is **shrug**. These tools are in need of being
updated
for
1.9.x
I use flay/reek/flog with a small rake prelude which convert the files
by modifying the new hash syntax, essentially
gsub!(/(\w+):\s+/u, ':\1 => ')
_md
--
Posted via http://www.ruby-forum.com/\.
IF ONLY it were that simple. ![]()
If you guys wanted flay/flog/reek to work on 1.9 sooner rather than later... patches welcome.
On Jul 16, 2012, at 09:36 , Michel Demazure wrote:
This question came up about three months ago at the nashville ruby
meetup.
The short answer is **shrug**. These tools are in need of being
updated
for
1.9.xI use flay/reek/flog with a small rake prelude which convert the files
by modifying the new hash syntax, essentiallygsub!(/(\w+):\s+/u, ':\1 => ')